This extension may have been corrupted.

[Praveen Bolla]

We’ve had a Chrome extension in use for quite a while, but after yesterday’s update, some Windows users started seeing the message, "This extension may have been corrupted." The issue continues even after attempting repairs or reinstalling. However, it worked again once we rolled back to the previous version.

For additional context, just before this update, we accidentally uploaded a buggy package to the Chrome Web Store that was missing JS files, which was rightly rejected.

[Praveen Bolla]

For additional context, we initially deferred publishing after realizing we had uploaded the wrong package. Once it was rejected, we re-uploaded the correct package with the same version number.

[Zach Warneke]

Hi,

Is the issue only happening on Windows? There's a known bug where content verification may fail on Windows if your extension contains any files with really long paths. If content verification fails, it will lead to Chrome thinking the extension is corrupted, which could explain what you're seeing.

Zach

[Praveen Bolla]

Currently, we're only seeing the issue on a few Windows machines, not all. Is there any way we can identify the specific factor causing the issue?

[Zach Warneke]

I don't believe the logs for corruption are very detailed but will check with some others to verify. Because of that, it's not easy to identify which file(s) in the extension are becoming corrupted.

I would suggest checking the list of files that changed between the good version and the version with corruption. If there are any with particularly long file paths, you should try renaming/removing them, re-publishing, and see if the issue persists.

Zach