[Bug] Data Integrity Check "GeoIp2Updater.vue" never resolves

[brainfoolong]

What happened?

I am on windows, installed normally (no docker).
With 5.6.0 (Maybe even before) this data integrity cannot be resolved.

It says plugins/GeoIp2/vue/src/Geoip2Updater/GeoIp2Updater.vue should be deleted, when i delete it, it says it is missing.

I tried already replacing the file with a fresh download from 5.6.0, same issue.

Before delete

After delete

Our installation is well aged, it exists since all this was named piwik. Maybe we miss some related config changes, i don't know. No other errors in system integrity checks visible.

Systemcheck log attached.

matomo_system_check.txt

What should happen?

It should be resolveable. Either it should need to be deleted or not.

How can this be reproduced?

Goto this local url "System Checks" -> index.php?module=Installation&action=systemCheckPage

Matomo version

5.6.0

PHP version

8.4

Server operating system

Windows Server 2019

What browsers are you seeing the problem on?

No response

Computer operating system

No response

Relevant log output

Validations

• Read our Contributing Guidelines.
• Follow our Security Policy.
• Check that there isn't already an issue that reports the same bug to avoid creating duplicates.
• The provided steps to reproduce is a minimal reproducible of the Bug.

[sgiehl]

Hm. This sounds strange. I've checked the last releases and the file is always listed in the generated manifest. So it should not be reported as file to be removed 🤔
Can you check if the file config/manifest.inc.php includes an entry for plugins/GeoIp2/vue/src/Geoip2Updater/GeoIp2Updater.vue in you install?

[brainfoolong]

I can confirm, it is in there. But, its case is different to the file on disk.

In config

plugins/GeoIp2/vue/src/GeoIp2Updater/GeoIp2Updater.vue

On my disk

plugins/GeoIp2/vue/src/Geoip2Updater/GeoIp2Updater.vue

The difference lies in GeoIp2Updater

[sgiehl]

That's strange. The folder should have a capital I in it. Not sure why it was created differently for you. Would you try renaming the folder? That should fix the issue.

[brainfoolong]

Yep, that fixed it. As i said, maybe this was named like that in the past (our installation is originally from piwik times). You can close this if you don't need further information.

[sgiehl]

Ok. Thanks for the confirmation. I can vaguely remember there had once been an issues with something like that, for a version in the past. But I can't fully remember. I'll close the issue for now. If it ever pops up again, please let us know, so we can check if we might need to implement additional checks/safeguards to prevent that from happening.