Hi, I uploaded an extension to the edge store (a while ago) and I find that anyone who installs it gets a CRX_SIGNATURE_VERIFICATION_FAILED error. The same extension, when uploaded to the chrome web store, works perfectly fine. Does someone have an idea as to what is going on and why this error appears for everyone?
Hi @SanderRonde-3338 ,
According to your description, I tried installing the extension you mentioned and found that such a problem does exist. And I found the files download from these two stores have some difference in size(about 0.4M), like this below. so I'm not sure if you ported it correctly from chrome store to edge store.
About the related doc, did you correctly refer to Port a Chrome extension to Microsoft Edge?
Glad you were at least able to reproduce the issue. I'm fairly sure that this size difference is because of a difference in versions between the extensions. The short version of the story is that I had a bunch of functionality which made my extension great (user-controlled access to the chrome APIs), then Google said it wasn't allowed anymore (because dynamically asking for permissions was no longer allowed) and I had to remove all of that code from the extension. The new version (without this code) was uploaded to the chrome store, while the old version is still in the edge store. There might also be some other differences in the exact packaging procedure but I don't fully remember. IIRC the edge extension also includes some images the chrome extension doesn't.
What is even more interesting is that this exact version of the extension used to work before. I released the current version about 3 years ago and it kept working without me touching it until it suddenly broke. I didn't upload a new version whatsoever.
Hi @SanderRonde-3338 ,
If this is the case, I think you should refer to the documentation I mentioned above for port a Chrome extension to Microsoft Edge. As far as I know, Edge changed its engine in April about two years ago and is now based on chormium. I think you have to follow the rules of its extension development.
Therefore, you can try to update your extension and re-upload to Edge add-ones store according to the documentation mentioned above.
13 people are following this question.
