Extension installed via Google Cloud is disabled in Chrome version 123

[Vadim Stavkin]

Our extension is rolled out to users via Google Cloud policy InstallForceList. 

We self host this extension on our internal server. The extension still uses manifest V2.

After updating Chrome to version 123(latest stable), our extension started to get disabled by Chrome.

We found that if Chrome is opened on the Extensions page first, the extension will be enabled. However if any other page is opened first, the extension will stay disabled.

Has someone else noticed that their self-hosted extension is disabled? Were there any changes related to extensions introduced in version 123?

[Joseph Flood]

Hi Vadim,

Yes both I and Don have experienced this in the recent week or so.

Neither of us have received a response from the team yet.

[David]

Same here.

Not sure why it is not being addressed by the team.

Seems like a chromium related bug (v.123) or a feature flag that is being tested poorly.

[Owen Min]

This s related to issues.chromium.org/u/1/issues/331061788, we are working on the fix.