crx: Packed & signed .crx does not work in Chrome
Chrome version 71.0.3578.98 (Official Build) (64-bit) OS: macOS 10.14.2 node v11.5.0 crx 3.2.1
When trying to pack a crx with the following command: npx crx pack dist/chrome -p chrome.pem > dist/voc-api-chr.crx , the .crx gets generated without errors.
When I try to load the .crx in Chrome however, I get the error Package is invalid: "CRX_HEADER_INVALID".
Packing with Chrome manually works fine.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 2
- Comments: 29 (4 by maintainers)
Thanks, that’s a problem for sure.
I will try to have a look into it next week.
Any chance to get an official release now that it’s merged?
@miguelespinoza I only found it after looking through the list of commits between the Chrome 72.x and Chrome 73.x releases. 😦
Wow, @joscha quickly reviewed last changes and v5.0.0 is on npm now 😃!
I hope i did not screw up anything while publishing 🤞 😃. It would be great if people could confirm that it works ok, so we can (finally) close this issue.
@miguelespinoza Chrome 73 requires the CRXs to be packed with the CRX3 header format, which #98 addresses. I’m hoping it’s merged soon!
Would like to see an official release so we can update packages 😃
Just info this can be marked as fixed tested it on my extension and correctly it can be installed on Canary and normal version of the Chrome
@oncletom it may work, but i did not know about it and i added tag only after publishing to npm 😦.
@philmacdonald2 thanks for the info. If v5.0 from npm creates CRX that works in Chrome that’s OK.
If Update Manifest does not work, new bug issue can be created.
Thanks everyone!
omg please 🙏 still waiting for an official release
I guess this should be marked as fixed now, right? @th0rgall, @Mathieuu, @miguelespinoza can you confirm that latest master works OK now?