Some files have not passed the integrity check: "Invalid files" during integrity scan

Adding some apps/integrations seem to add mime file types:

Technical information
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix


  • core
    - core/js/mimetypelist.js
    - core/img/filetypes/dwg.svg
    - core/img/filetypes/3dm.svg
    - core/img/filetypes/3ds.svg
    - core/img/filetypes/3mf.svg
    - core/img/filetypes/bim.svg
    - core/img/filetypes/brp.svg
    - core/img/filetypes/dae.svg
    - core/img/filetypes/fbx.svg
    - core/img/filetypes/fcstd.svg
    - core/img/filetypes/glb.svg
    - core/img/filetypes/gltf.svg
    - core/img/filetypes/ifc.svg
    - core/img/filetypes/igs.svg
    - core/img/filetypes/obj.svg
    - core/img/filetypes/off.svg
    - core/img/filetypes/ply.svg
    - core/img/filetypes/stp.svg
    - core/img/filetypes/stl.svg
    - core/img/filetypes/wrl.svg
    - core/img/filetypes/mtl.svg

There seems to be a lack of a way to update the proper checksums based on that, as these files are simply not expected, and thus cause the relevant errors to be thrown.

Similarly, for whatever reason a .htaccess file went missing, and doesn’t get installed even if removing and reinstalling the app:

  • libresign
    - vendor/tecnickcom/tcpdf/tools/.htaccess

The problem with bugs like these: they get people used to the error messages, so if truly malicious code modifications happen, they will be ignored and dismissed.
So it would be very important that users are empowered to fix issues like these after verifying that everything is indeed OK.

The suggestions shown, do not solve the issue…

…is there any solution planned?

1 Like

What version of NC?

Have you filed a bug report?

Same problem here. Did you solve it?

same problem but a massive list after my upgrade to version 27. Its pretty much the entire 3rd party app list and more.

The error is the same for all of the entries:

[expected] =>
[current] => very long alphanumeric string

What do I need to do to fix this?