Some Users of Extension get "This extension may be corrupt"

[Tim Heflin]

For our extension (https://chromewebstore.google.com/detail/keeper%C2%AE-password-manager/bfogiafebfohielmmehodmfbbebbbpei) some users are receiving the "This extension may be corrupt" error message. We have not been able to reproduce this locally on our end. 

Some info from other sources of the cause:

- This could be some bug from version 135. We have had additional reports recently, but no confirmation of what version the user was on.

- This could be a file system cleaner or antivirus messing with the files in our extension

My question is what is typically the cause for this error message? Is this an issue with naming a file wrong in the extension's source? Has anyone else seen this issue and have a way to resolve this? Is there a way for the extension to report this issue to us? (I suspect no because the extension is in a state where the user needs to re-install, but I'm open to a way to log this issue)

[Oliver Dunk]

Hi Tim,

There was an issue in Chrome 135 and earlier where making requests for chrome-extension:// resources with the Range header could cause corruption: https://issues.chromium.org/405286894. This sounds similar, so it might be worth taking a look to see if that could apply in your case. This is now fixed (since Chrome 136 in May) but that would of course only benefit users who have updated Chrome.

Unfortunately, there isn't an easy way for the extension to self-report this or to gather more information. However, if the above issue doesn't seem relevant, please do open a Chromium bug and share the link and I can make sure our team takes a look.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/7fae6a0c-2c18-4c97-bc85-bf67db0fe7f1n%40chromium.org.

[Tim Heflin]

Thanks for the reply Oliver. In that issue link, the steps to reproduce states that this issue occurs on install of the extension from the crx file. When our users report this issue, it's from using the extension over some amount of time and eventually the extension is seen as corrupted, so I don't think it's necessarily the same. The other issue is that we have not been able to get good steps to reproduce from users or internally. 

Should we reopen/message one of these issues? They seem similar to the issue that we are having:
- https://issues.chromium.org/issues/356190940
- https://issues.chromium.org/issues/353554183

[Oliver Dunk]

Hi Tim,

Apologies for the delayed reply.

My understanding is that doing a fetch request with a `Range` header causes this issue, and it surfaced on install for that particular extension because of when the fetch requests were run.

Could you audit your extension to see if it is possible you are making a fetch request with an explicit Range header at a different time?

If not, I think it would be reasonable to open an issue, but I'd probably lean towards a new one and we can always merge into an existing one if we need to :)

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB