Can we no longer install .crx files manually if they're not in the Chrome Store?

1,847 views
Skip to first unread message

Tim Bessie

unread,
Oct 4, 2022, 6:34:12 PM10/4/22
to Chromium Extensions
Hi all...

My project has a Chrome extension that we supply to customers, but not through the Chrome store.  Our customers use the "drag .crx file to the Extensions screen" method to install it.

Given the changing requirements for the manifest file, I updated my manifest file for our extension and packed it and installed it.

However, the app is not enabled, and I'm not able to enable it, as Chrome says it's not in the Chrome store.

This didn't used to be a requirement.

Is this a new requirement?  Or are there items I need to add to the manifest to make this possible now?

- Tim

Robbi

unread,
Oct 4, 2022, 6:53:03 PM10/4/22
to Chromium Extensions, timb...@gmail.com
I think it can still do on Linux OS.
If your customers use Windows instead, you can suggest them to switch to SRWare Iron or FlashPeak Slimjet.
Both are Chromium-based browsers, so they won't be too shocked by the change.

Tim Bessie

unread,
Oct 4, 2022, 7:01:07 PM10/4/22
to Chromium Extensions, Robbi, Tim Bessie
Yeah, our base is mostly on Windows, with some on Macs.  I don't think anyone uses Linux.

If this is a new requirement (and who would know if it is, by the way?), we might have to make it available in the Chrome Store, I guess.

- Tim

hrg...@gmail.com

unread,
Oct 4, 2022, 8:05:49 PM10/4/22
to Chromium Extensions, timb...@gmail.com, Robbi
The ability to load local CRX files was removed from Chrome on Windows and Mac about 4 years ago, around version 68, I think.

Tim Bessie

unread,
Oct 4, 2022, 8:17:42 PM10/4/22
to Chromium Extensions, hrg...@gmail.com
That's odd, because I was able to install the old .crx file into the current version of Chrome (106).

It was only when I repacked it that it wouldn't install.  Perhaps it's based on the format of the .crx file and not on the Chrome version?

Installing the old .crx file was successful, but it marked the extension with a noficiation icon, which brought up a message about how future versions of Chrome wouldn't allow the extension to be run (starting December 2021 I think).

- Tim

Reply all
Reply to author
Forward
0 new messages