3 ms·

Enterprise editions of Chrome continue to have manifest v2 support, so this doesn't necessarily affect Google employees.

mh- 2y ago
Guess I know what I'm deploying in my enterprise of one seat.
- djhn 2y ago
  If anyone finds a good guide, this would be a great place to share it.
  - sharken 2y ago
    According to https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline https://developer.chrome.com/docs/extensions/develop/migrate... the message is this: June 2025: Chrome MV2 deprecation enterprise rollout
  - account42 2y ago
    People will do anything not to get eating, except getting rid of the beast.
  - lukasgraf 2y ago
    On macOS: # defaults write com.google.Chrome.plist ExtensionManifestV2Availability -int 2 This will continue to allow MV2 extensions for your Chrome instance. Confirm the policy has been set by checking chrome://policy. See [1] for possible values. Now, because uBO is now disabled in the Chrome Web Store, you also need to install it as a "forced extension" (the way extensions are deployed in enterprise environments). Install the extension according to the section "Use a preferences file" in [2]: - Create a file named cjpalhdlnbpafiamejdnhcphjbkeiagm.json - Place it in ~/Library/Application Support/Google/Chrome/External Extensions/ - With content: { "external_update_url": "https://clients2.google.com/service/update2/crx" } You'll need to create the "External Extensions" directory, set file permissions according to docs, restart Chrome. The file name contains the extension ID to be installed, which you can verify from the submission URL of this post. Upon Chrome restart, it should notify you with a message in the top right that an extension was forcibly installed. The ExtensionManifestV2Availability definitely still works for now, but it's been a about a month since I used the preferences file way of installing the extension on a new device. YMMV. [1] https://chromeenterprise.google/policies/#ExtensionManifestV2Availability https://chromeenterprise.google/policies/#ExtensionManifestV... [2] https://developer.chrome.com/docs/extensions/how-to/distribute/install-extensions?hl=en#preferences https://developer.chrome.com/docs/extensions/how-to/distribu...
    - seanp2k2 2y ago
      Nice, works for now, I'm sure they'll pull the rug on this solution too in under a year. I'm switching browsers, I hate ads more than I like Chrome. Sounds like June 2025 is the real date when it'll no longer be possible to use manifest v2 extensions per https://blog.chromium.org/2024/05/manifest-v2-phase-out-begins.html https://blog.chromium.org/2024/05/manifest-v2-phase-out-begi...

mh- 2y ago

Guess I know what I'm deploying in my enterprise of one seat.

djhn 2y ago
If anyone finds a good guide, this would be a great place to share it.
- sharken 2y ago
  According to https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline https://developer.chrome.com/docs/extensions/develop/migrate... the message is this: June 2025: Chrome MV2 deprecation enterprise rollout
- account42 2y ago
  People will do anything not to get eating, except getting rid of the beast.
- lukasgraf 2y ago
  On macOS: # defaults write com.google.Chrome.plist ExtensionManifestV2Availability -int 2 This will continue to allow MV2 extensions for your Chrome instance. Confirm the policy has been set by checking chrome://policy. See [1] for possible values. Now, because uBO is now disabled in the Chrome Web Store, you also need to install it as a "forced extension" (the way extensions are deployed in enterprise environments). Install the extension according to the section "Use a preferences file" in [2]: - Create a file named cjpalhdlnbpafiamejdnhcphjbkeiagm.json - Place it in ~/Library/Application Support/Google/Chrome/External Extensions/ - With content: { "external_update_url": "https://clients2.google.com/service/update2/crx" } You'll need to create the "External Extensions" directory, set file permissions according to docs, restart Chrome. The file name contains the extension ID to be installed, which you can verify from the submission URL of this post. Upon Chrome restart, it should notify you with a message in the top right that an extension was forcibly installed. The ExtensionManifestV2Availability definitely still works for now, but it's been a about a month since I used the preferences file way of installing the extension on a new device. YMMV. [1] https://chromeenterprise.google/policies/#ExtensionManifestV2Availability https://chromeenterprise.google/policies/#ExtensionManifestV... [2] https://developer.chrome.com/docs/extensions/how-to/distribute/install-extensions?hl=en#preferences https://developer.chrome.com/docs/extensions/how-to/distribu...
  - seanp2k2 2y ago
    Nice, works for now, I'm sure they'll pull the rug on this solution too in under a year. I'm switching browsers, I hate ads more than I like Chrome. Sounds like June 2025 is the real date when it'll no longer be possible to use manifest v2 extensions per https://blog.chromium.org/2024/05/manifest-v2-phase-out-begins.html https://blog.chromium.org/2024/05/manifest-v2-phase-out-begi...