CRX3 Announcement?

492 views
Skip to first unread message

PhistucK

unread,
Dec 26, 2018, 5:00:48 AM12/26/18
to Chromium-extensions
Looks like the CRX format is getting an update to CRX3 in Chrome 75 and I have not seen any announcement anywhere (I might have mis-searched). Searching a bit, it is hidden in the Chrome Enterprise 71 release notes.

I think there should be a public service announcement, here and in the Chromium blog, including the technical changes (there are third-party libraries for creating CRX files and they should know about it) and ideally, the benefit they provide.


Thank you.

PhistucK

sim...@chromium.org

unread,
Dec 26, 2018, 1:15:05 PM12/26/18
to Chromium Extensions, Joshua Pawlicki
Yeah, we should put together some information about the new format +waffels@

Darren Govoni

unread,
Dec 26, 2018, 2:00:40 PM12/26/18
to sim...@chromium.org, Chromium-extensions, waf...@chromium.org
Please provide a command line script to build this .crx file from our code trees. Thanks!

I use one I found on github (old) that is probably obsolete for this new format.

--
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 post to this group, send email to chromium-...@chromium.org.
Visit this group at https://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/777ab6d1-6be4-492c-a5c8-d528db7b5c1b%40chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

Devlin Cronin

unread,
Dec 27, 2018, 12:05:10 PM12/27/18
to Chromium Extensions, sim...@chromium.org, waf...@chromium.org
waffles@ looks to be out until the new year.  I'll still defer to them for the bulk of the information/documentation here, but one quick note: Chrome should already create CRX3 packages when packing an extension normally (e.g., through --pack-extension command line flag or the chrome://extensions page).  Any tools that use a modern version of Chrome to do the packing should be creating CRX3-format packages.  (Note that the extension is the same, ".crx".)


On Wednesday, December 26, 2018 at 11:00:40 AM UTC-8, Darren Govoni wrote:
Please provide a command line script to build this .crx file from our code trees. Thanks!

I use one I found on github (old) that is probably obsolete for this new format.

On Wed, Dec 26, 2018 at 1:15 PM <sim...@chromium.org> wrote:
Yeah, we should put together some information about the new format +waffels@

On Wednesday, December 26, 2018 at 2:00:48 AM UTC-8, PhistucK wrote:
Looks like the CRX format is getting an update to CRX3 in Chrome 75 and I have not seen any announcement anywhere (I might have mis-searched). Searching a bit, it is hidden in the Chrome Enterprise 71 release notes.

I think there should be a public service announcement, here and in the Chromium blog, including the technical changes (there are third-party libraries for creating CRX files and they should know about it) and ideally, the benefit they provide.


Thank you.

PhistucK

--
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-extensions+unsub...@chromium.org.
To post to this group, send email to chromium-extensions@chromium.org.
Message has been deleted

PhistucK

unread,
Apr 26, 2019, 5:46:28 AM4/26/19
to xbrows...@gmail.com, Chromium Extensions, Simeon Vincent, Joshua Pawlicki
The documentation link you mentioned is unrelated to the binary format version, so it is up to date. The manifest_version to use is still 2. 3 is not yet (fully) developed.

PhistucK


On Fri, Apr 26, 2019 at 11:43 AM <xbrows...@gmail.com> wrote:
After upgrading chromium to 73.0.3683.103 I started getting CRX_HEADER_INVALID errors when attempting to manually install my extension's CRX file generated from the Play Store (for testing purposes), which worked fine in 71.*. I was obviously surprised at this, but after some investigation it looks like v73 is enforcing CRX3, when the manifest version used by my extension is "2" - as specified in the documentation.

I am surprised at the lack of information available on CRX3 despite it being enforced since v73 and the current stable release of Chrome is v74. The documentation is clearly out of date (who is responsible for updating this?) and that fact I have to go hunting around the chromium groups for information is not exactly great.

Could you please direct me to where I can find information regarding the manifest format for CRX3 so I can get my extension to install again?

Thank you.


On Thursday, December 27, 2018 at 5:05:10 PM UTC, Devlin Cronin wrote:
waffles@ looks to be out until the new year.  I'll still defer to them for the bulk of the information/documentation here, but one quick note: Chrome should already create CRX3 packages when packing an extension normally (e.g., through --pack-extension command line flag or the chrome://extensions page).  Any tools that use a modern version of Chrome to do the packing should be creating CRX3-format packages.  (Note that the extension is the same, ".crx".)

On Wednesday, December 26, 2018 at 11:00:40 AM UTC-8, Darren Govoni wrote:
Please provide a command line script to build this .crx file from our code trees. Thanks!

I use one I found on github (old) that is probably obsolete for this new format.

On Wed, Dec 26, 2018 at 1:15 PM <sim...@chromium.org> wrote:
Yeah, we should put together some information about the new format +waffels@

On Wednesday, December 26, 2018 at 2:00:48 AM UTC-8, PhistucK wrote:
Looks like the CRX format is getting an update to CRX3 in Chrome 75 and I have not seen any announcement anywhere (I might have mis-searched). Searching a bit, it is hidden in the Chrome Enterprise 71 release notes.

I think there should be a public service announcement, here and in the Chromium blog, including the technical changes (there are third-party libraries for creating CRX files and they should know about it) and ideally, the benefit they provide.


Thank you.

PhistucK

--
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 post to this group, send email to chromium-...@chromium.org.

--
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 post to this group, send email to chromium-...@chromium.org.
Message has been deleted
Message has been deleted
Message has been deleted

Don Schmitt

unread,
May 8, 2019, 8:16:12 PM5/8/19
to Chromium Extensions, xbrows...@gmail.com, sim...@chromium.org, waf...@chromium.org
I see now that you've been writing version 3 into CRX files since 3 since build 64, so that's a relief and most of our customers are fine.  But again, where should I have looked to get a heads-up on this breaking change?  It seems like there should have been an explicit notification with a timeline.  Maybe there was?

On Wed, May 8, 2019 at 1:45 PM donaddon <donc...@gmail.com> wrote:
By V3, I mean CRX3, sorry for mixing the terminology.

On Wednesday, May 8, 2019 at 1:40:20 PM UTC-7, donaddon wrote:
Wow, good thing I got lucky and ran across this.  Did I read correctly (hidden in that Enterprise blog) that in Chrome 75 all privately hosted extensions will no longer be installed if they weren't packaged with V3?  This would be a rather quick move for a breaking change with little announcement.  And if so, this will be a _major_ issue for many of our enterprise customers who are just going to lose their installs when that happens.  Ironically, a significant reason these customers use privately hosted versions is precisely so they can _avoid_ accidentally picking up breaking changes from the web store.

Did we miss a more public announcement or documentation that gives the specific time-frame of this breaking change and any other details?

Thanks!

Joshua Pawlicki

unread,
May 8, 2019, 11:14:18 PM5/8/19
to Chromium Extensions, xbrows...@gmail.com, sim...@chromium.org, waf...@chromium.org
I think we struggled to find a good place to communicate this change. The enterprise release notes for each milestone since M68 have contained a description and timeline for the change (example), and we've been pointing people there. I think further communications are being prepared in the upcoming weeks.

Also just to clarify - extensions that were installed as CRX2s will continue to run (they won't be disabled or uninstalled). Once the extension is unpacked by Chrome, the packaging format doesn't matter. What will break is that Chrome will not do new installs involving CRX2 packages, or update out-of-date extensions to newer versions that are packaged as CRX2s.

There is a user policy to temporarily opt-out or opt-in to the new behavior, available starting in M73: ExtensionAllowInsecureUpdates (see the link to the enterprise release notes for details).
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.

--
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-extensions+unsub...@chromium.org.

--
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-extensions+unsub...@chromium.org.

Don Schmitt

unread,
May 8, 2019, 11:35:32 PM5/8/19
to Joshua Pawlicki, Chromium Extensions, xbrows...@gmail.com, sim...@chromium.org, waf...@chromium.org
Perfect, thanks for the tip and clarification Joshua, I'll keep a watch on that enterprise release page for future updates in addition to here.  Cheers! - Don


To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.

--
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.

--
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.

--
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.
Reply all
Reply to author
Forward
0 new messages