Hi,
do you have a backlog for this to be adjusted/fixed?
We plan to fix this in future updates. For now, you can ignore this error as it does not affect functionality.