Windows- & MacOS-specific CRX install failure

[Warren Halderman]

I was wondering why my extension update wasn't being propagated for weeks after release. Turns out there was a filename casing issue that only affected Windows and MacOS users.

You may already know, but most Linux-based file systems and (to my surprise) ZIP archives are case-sensitive and consider "url.js" and "URL.js" to be different files, but Windows and MacOS consider them to be the same, leading to invisible bugs when developing and testing on Linux-based operating systems...

When validating newly uploaded packages, would it be possible to also verify that there are no "duplicate" filenames in any directory of the archive? I realize it would only help a minuscule portion of developers, but it would be incredibly helpful.

[Oliver Dunk]

Hey Warren,

Thanks for calling that out - it's a great suggestion!

We don't have a public bug tracker for the Chrome Web Store, but I've filed your request internally, and hopefully it is something we might be able to look at some time soon.

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/c0cfe658-430f-46a6-ba47-cb2b566b10e0n%40chromium.org.

[Warren Halderman]

Thank you Oliver, hopefully it’s implemented and saves my butt in the future. 🙂

Warren

On Feb 20, 2026, at 17:20, Oliver Dunk <olive...@google.com> wrote: