Manifest V3 extensions FAQ

As Google will deprecate Manifest V2 extensions by June 2023 , this might impact your existing automations that use our current Manifest V2 extensions for Chrome and Edge browsers. We plan to publish Manifest V3 extensions with the upcoming Automation 360 v.26 release to help you start switching to Manifest V3 extensions.

What is Manifest V2 extension deprecation?

A manifest is a specification using which browser extensions are built. As Google is deprecating Manifest V2 extensions by June 2023, we recommend you plan to switch to Manifest V3 extensions, which provide enhanced security, privacy, and performance. The deprecation might impact your existing automations that use Manifest V2 extensions for Google Chrome and Microsoft Edge browsers. Hence, we recommend that you plan to switch to Manifest V3 extensions.

See the following resources for more information:

Google Chrome: Manifest V2 support timeline
Microsoft Edge: Overview and timelines for migrating to Manifest V3

When will the Manifest V2 support end?

In June 2023, Manifest V2 based Google Chrome and Microsoft Edge browser extensions will stop functioning. However, you can update the group policy to extend the use of Manifest V2 extensions until Jan 2024. See Manifest V3 transition timeline.

All support for Manifest V2 ends in Jan 2024(Manifest V3 transition timeline) and you must switch to Manifest V3 based Google Chrome and Microsoft Edge browser extensions by then.

To extend support for Manifest V2 until January 2024, see Manually upgrade from Manifest V2 to V3 extensions for Chrome and Edge

How do I know if I am going to be impacted by the deprecation?

If you are using any or all of the following features on Google Chrome or Microsoft Edge browsers, you will be impacted by the Manifest V2 deprecation.

Automation of web applications through Universal Recorder or Browser package
User interface based triggers
Bot Agent device registration with the Control Room
Packages that use window titles, for example, OCR and Mouse Click

Do I have to do anything in advance of the deprecation?

To avoid being affected by the deprecation, you can choose one of the following options:

What should I do to extend the group policy to continue using Manifest V2 extensions till Jan 2024?

Use the group policy to extend support for Manifest V2 extensions until Jan 2024. For more information, see manifest-v3-support-overview.html#tpc-manifest-v3-support-overview__extend-mv2-through-group-policy | Manifest V3 transition timeline.

Will the Manifest v2 extensions be automatically updated to V3 or do I have to manually add V3 extensions to the browser?

If you are on Automation 360 v.26 or later, and if you have updated to Bot Agent 21.222 or later, you will be automatically updated to Manifest V3.
If you are on Automation 360 v.25 and earlier, you must manually upgrade the Manifest V2 to V3.
See Manually upgrade from Manifest V2 to V3 extensions for Chrome and Edge.

Which Automation 360 versions are certified for upgrading from Manifest V2 to V3 extensions?

The following versions are certified for upgrade:

v.25
v.24
v.23
v.22

I plan to continue with Automation 360 v.25, so what should I do to continue using MV2 extensions?

You can continue to use Manifest V2 extension only till Jan 2024.See Manifest V3 transition timeline. You will have to perform some manual steps to extend the support.

For more information, see Manually upgrade from Manifest V2 to V3 extensions for Chrome and Edge.

What about the automations that I have already built using Chrome or Edge?

If your automations are dependent on browser extensions, you must either upgrade to Manifest V3 extensions or extend support for Manifest V2 extensions for your automations to continue working after the deprecation.

Do I need to update the Recorder package in the bots or will they continue to work with the earlier versions?

The Recorder package will work as intended, so there is no need to update the package.

I am using Automation 360 Cloud, so will my automations be impacted by the deprecation?

Cloud deployments are automatically updated to the upcoming Automation 360v.26 release, which includes Manifest V3 extensions. The Automation 360 v.26 Bot Agent will refer to Manifest V3 extensions.

注： If the Automatically update all bot agents option in your Control Room settings is disabled on your device, you will not be automatically updated to Manifest V3 extensions. So ensure that this option is enabled to receive automatic updates. Alternatively, you have to install the Bot Agent manually on all the Bot Runner devices.

How does the deprecation impact my migration?

We recommend that you migrate to Automation 360 v.26, which uses Manifest V3 extensions by default.

If you are using Automation 360 v.25 or earlier, you must either upgrade to Manifest V3 extensions or extend Manifest V2 extensions before you migrate browser-based automations.

Will the URL for the extensions change? Will the URLs that I have added in the trusted list for proxy settings be impacted?

Yes, the URLs for the extensions are different for Manifest V2 and V3. Use the following URLs for Manifest V3:

Chrome: Google Chrome extension for Automation 360
Edge: Microsoft Edge extension for Automation 360

Will Manifest V2 extensions be retained after I upgrade to Manifest V3?

Until Jan 2024, you can continue to use the extensions. However, these extensions cannot be modified after December 2022, so Automation Anywhere will not be able to make any updates to these extensions after December 2022. See Manifest V3 transition timeline

If Enterprise 11 and Automation 360 are running on the same device , will there be any conflicts due to the Manifest V2 deprecation?

There will be no impact in such scenarios because the Manifest V3 extensions IDs are different for Enterprise 11 and Automation 360.

As I am currently on Cloud deployment, I'd prefer to continue using Manifest V2 extensions. Can I continue to use Manifest V2?

We recommend that you upgrade to the latest Automation 360 version to get the benefits of Manifest V3 extensions. However, if you still want to continue using Manifest V2 based extensions, ensure that you disable the Automatically update all bot agents option (in the Control Room settings) for all devices and ensure that users do not install the latest Bot Agent. This is required because the Automation 360 v.26 Bot Agent supports only Manifest V3 extensions.

Do I have an option to upgrade my devices in a phased or staggered manner?

Yes, you can upgrade your devices in a staggered manner to Manifest V3. You can disable the Automatically update all bot agents option for all devices and then select the devices individually for which you want to upgrade the Bot Agent.

Can I revert the upgrade from Manifest V3 to V2?

Yes, you can switch from Manifest V3 to V2. Update the JSON file with following Manifest V2 extension IDs:

Chrome V2 Extension ID: kammdlphdfejlopponbapgpbgakimokm
Edge V2 Extension ID: dbmodiepejcigljbmeebedkmegndokbk

See Switch Manifest V3 to Manifest V2 extension manually for more information.

My bot uses a Recorder package from an earlier Automation 360 version and has a hard-coded Manifest V2 extension ID in it. How do I change the extension ID?

When you update to Automation 360 v.26, the extension ID for Manifest V3 is updated automatically.

My application has IFrame with Content Security Policy enabled. Will “Run JavaScript” action run the JavaScript inside the iFrame?

With Manifest V3, Google has restricted access to IFrame where Content Security Policy (CSP) is enabled in target page. If your business application does not have CSP enabled, you will be able to run JavaScript inside the IFrame. If your business application has CSP enabled, you will not be able to run JavaScript inside the IFrame and the Run JavaScript action will timeout/fail.

What version of the browsers are supported for Manifest V3?

Manifest V3 is supported on Google Chrome and Microsoft Edge Version 91 and later.

I am currently on Automation 360 v.26. Can I switch to Manifest V2 extension?

Yes, you can switch to Manifest V2 extension while being on Automation 360 v.26. See Switch Manifest V3 to Manifest V2 extension manually for more information.

I am currently on Automation 360 v.26. Are there any settings that I have to configure to continue to avail the latest browser extension versions?

If you have an internet connection, you will continue to receive the updates through auto-updates. For offline support, contact Automation Anywhere support.

Will there be any impact to the remote agent that I have been using?

The remote agent installed with Automation 360 v.25 or earlier is not compatible with the Manifest V3 extension. You must install the latest Automation Anywhere remote agent and use the latest Recorder package. See Install remote agent: Recorder package version 2.8.6.