Packed & signed .crx does not work in Chrome

[thom4parisot]

Packed & signed .crx does not work in Chrome

[thom4parisot]

Thanks, that's a problem for sure.

I will try to have a look into it next week.

[arkon]

@miguelespinoza I only found it after looking through the list of commits between the Chrome 72.x and Chrome 73.x releases. :(

[dchancogne]

Any chance to get an official release now that it's merged?

[arkon]

@miguelespinoza Chrome 73 requires the CRXs to be packed with the CRX3 header format, which #98 addresses. I'm hoping it's merged soon!

[ahwayakchih]

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.

[MichalMeszaros]

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

[xvilo]

Would like to see an official release so we can update packages :)

[ahwayakchih]

I guess this should be marked as fixed now, right?
@th0rgall, @Mathieuu, @miguelespinoza can you confirm that latest master works OK now?

[oliv9286]

omg please 🙏 still waiting for an official release

[ahwayakchih]

@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!

[ahwayakchih]

@oncletom it may work, but i did not know about it and i added tag only after publishing to npm :(.

[Mathieuu]

Same problem

[miguelespinoza]

Yup, I'm seeing that issue as well.

On Chrome version 73.0.3683.75 (Official Build) (64-bit)
Worked fine in Chrome version 72.0.3626.119 (Official Build) (64-bit)

@oncletom any idea what could be causing this? I did a general search and didn't find anything

[miguelespinoza]

FYI, occurs in Google Canary Version 75.0.3737.0 (Official Build) canary (64-bit)

[miguelespinoza]

Interesting, thanks @arkon. I ended up using Chromes package method
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --pack-extension=

Any release notes from Chromium that would have made this obvious?

[thom4parisot]

I'm hoping it's merged soon!
Chrome 73 requires the CRXs to be packed with the CRX3 header format

I made one comment in #98, to make the default value for the manifest version to be equal to 3 as it sounds like a saner default.

[ahwayakchih]

Thanks for the info @MichalMeszaros!

[ahwayakchih]

@oncletom can you close this in spare time?

[arkon]

Might want to close this after a release is pushed out to NPM.

[ahwayakchih]

Someone with rights to publish on npm is needed :).

cc @oncletom, @jed, @joscha

[xvilo]

Just added this as a git repo in with npm, make sure you use master. Then it's usable :D Please see PavelVanecek/gulp-crx#27 for example :P - And I then required that with the specific branch in my own project where I needed it to be working :'))))

[joscha]

Someone with rights to publish on npm is needed :).
cc @oncletom, @jed, @joscha

Sorry, only have gh

[bvaughn]

Just an FYI for folks asking for this to be released– this package on NPM just points to the source:
https://github.com/oncletom/crx/blob/d54145fb74067a44d5f3ab6123dc4b1b130f36ee/package.json#L12-L15

So you can install the updated version directly from GitHub, e.g. ef150e8

yarn add -D -- git+https://github.com/oncletom/crx#ef150e8

[Deliaz]

I use the version from the master branch and it works well, thanks. But few modules (such as crx-webpack-plugin) depends on released version (which is 4.0.1 now).

Btw, for those who looking updated webpack wrapper: I have fork here: Deliaz/crx-webpack-plugin which points to the crx@master.

[kiastu]

@oncletom, @jed
Is there anything we can do to help speed the process of releasing on NPM?
Is there any blockers we can help with?

[jed]

@ahwayakchih, i've added you as an owner on npm.

[ahwayakchih]

Thanks @jed! I'll prepare new release as soon as #105 and then next one with updated CHANGELOG #106 are is merged :).

[philmacdonald2]

I can confirm it packs my extension in a usable format, but I don't deploy through the store - only through the ExtensionForceList

[thom4parisot]

@ahwayakchih did pushing a new git tag published a new npm release? I thought that was working 🤔 (thanks @jed for giving npm publishing permissions)