Manifest V3 extensions FAQ

As Google will deprecate Manifest V2 extensions by June 2024, this might impact your existing automation that use the current Manifest V2 extensions for Google Chrome and Microsoft Edge browsers.

We have published Manifest V3 extensions with the 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. Google is deprecating Manifest V2 extensions by June 2024 for Google Chrome. To know about Microsoft Edge Manifest V2 extensions timelines, see Overview and timelines for migrating to Manifest V3. The deprecation might impact your existing automation that use Manifest V2 extensions for Google Chrome and Microsoft Edge browsers. So, we recommend that you plan to switch to Manifest V3 extensions, which provide enhanced security, privacy, and performance.
See the following resources for information on Manifest V2 extensions deprecation timelines: :
When will the Manifest V2 support end?
In June 2024, Manifest V2 extensions for Google Chrome will stop functioning. Starting on October 23, 2023, we will deprecate support for Manifest V2 extensions on Automation 360 v.26 and later releases. After this date, we will not address any issues relating to Manifest v2 extensions. For Microsoft Edge Manifest V2 extension timelines, see Overview and timelines for migrating to Manifest V3 for more information.

Support for Manifest V2 for Google Chrome ends in Jan 2024 (see Manifest V3 transition timeline). To know about Microsoft Edge Manifest V2 extensions timelines, see Overview and timelines for migrating to Manifest V3. You must switch to Manifest V3 based Google Chrome and Microsoft Edge browser extensions by then.

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 Browser variables, for example, Recorder, 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:
  • Update to Automation 360 v.26, which includes the latest Manifest V3 extensions.
  • Switch to Manifest V3 extensions before June 2023 if you are using Google Chrome. For Microsoft Edge Manifest V2 extensions timelines, see Overview and timelines for migrating to Manifest V3. .
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 update the Manifest V2 to V3. See Manifest extension manual upgrade. .
Which Automation 360 versions are certified for updating from Manifest V2 to V3 extensions?
The following versions are certified for the update:
  • 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 for Google Chrome (see Manifest V3 transition timeline). To know about Microsoft Edge Manifest V2 extensions timelines, see Overview and timelines for migrating to Manifest V3.
What about the automations that I have already built using Chrome or Edge?
If your automations are dependent on browser extensions, you must update to Manifest V3 extensions.
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 Automation 360 v.26 release, which includes Manifest V3 extensions. The Bot Agent in v.26 refers to Manifest V3 extensions.
Note: 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 update to Manifest V3 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:
Will Manifest V2 extensions be retained after I update to Manifest V3?
MV2 extensions will be retained for Google Chrome and Microsoft Edge browsers. However, these extensions cannot be modified after December 2022. Ensure that you continue using MV3 extensions. See also: Manifest V3 transition timeline.
Note: If you are on Automation 360 v.26 release and using Bot Agent 21.222, you will see both Manifest V2 and Manifest V3 registry entries in the Windows Registry.
  • You can remove the Manifest V2 entry from Windows Registry by uninstalling the existing Bot Agent 21.222 and installing the Bot Agent 21.222 again.
  • You can remove the Manifest V2 extension from the Extensions page.

Uninstalling the Bot Agent will remove both Manifest V2 and Manifest V3 extensions.

See Uninstall or remove apps and programs in Windows.

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.
Do I have an option to update my devices in a phased or staggered manner?
Yes, you can update 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 update the Bot Agent.
I had switched from Manifest V3 to V2 extensions for Automation 360 v.26. Can I now update to Manifest V3 extensions when I update Automation 360 to v.27?
When you update to Automation 360 v.27, the corresponding Bot Agent is also updated. Manifest V3 extensions are installed with the latest version of Bot Agent.

Additionally, ensure that you select the Enable Automation 360 extension for this browser profile option on Google Chrome and Microsoft Edge browsers. See Manage multiple browser profiles for Manifest V3 extension.

Note: If you are currently using Manifest V2 extensions or earlier versions, we recommend that you update and use the Manifest V3 extension.
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 the 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 or 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. 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 automatic updates.
Can I use MV3 extension offline or without internet connection?
MV3 extensions are automatically installed when you update the Bot Agent to the latest version. MV3 based offline extensions are available for:For additional help, 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 Automation Anywhere remote agent for Citrix 2.0: Recorder package version 2.8.6.

What are the prerequisites to configure the browser extension settings?
Following are the prerequisites to configure the browser extension settings:
  • Bot Agent version 21.222 or later.
  • You must have installed the Bot Agent with installation type as system-wide.
How do I remove the Manifest V3 group policy?
For Google Chrome: Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist] and remove the entries that contain bboccnojhhoegfffpcllbeigipedjedf as the extension ID.
For Microsoft Edge: Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist] and remove the entries that contain fnmjcdajlonpigpcfnemeikipmolbfii as the extension ID.
Restart the browser for the changes to take effect.
After updating to Automation 360 v.26, do I have to disable Manifest V2 extensions?
When you update to Automation 360 v.26, Manifest V3 extension is installed automatically, without impacting the already installed Manifest V2 extension. Both Manifest V2 and V3 extensions can coexist. The Manifest V3 extension does not interfere with Manifest V2 extensions. You can remove the Manifest V2-based extensions as needed.
How do I remove the MV2 extension?
For Google Chrome: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Chrome\. Expand Extensions folder and remove the folder by name kammdlphdfejlopponbapgpbgakimokm.
For Microsoft Edge: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Edge. Expand Extensions folder and remove the folder by name dbmodiepejcigljbmeebedkmegndokbk.
Alternatively, go to the Extensions page of your respective browser and remove the entry related to Manifest V2.
How do I remove the MV3 extension?
For Google Chrome: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Chrome\. Expand Extensions folder and remove the folder by name bboccnojhhoegfffpcllbeigipedjedf.
For : Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Edge. Expand Extensions folder and remove the folder by name bboccnojhhoegfffpcllbeigipedjedf.
Alternatively, go to the Extensions page of your respective browser and remove the entry related to Manifest V3.
How do I force-enable Google Chrome or Microsoft Edge extension for user-specific Bot Agent instances?
You can force-enable the Manifest V3 extension on Google Chrome or Microsoft Edge by running the .reg files for Manifest V3. See Manifest extension manual upgrade.
How do I add an extension force group policy if another extension policy has already been added by my IT team?
If a key by name 1 is already present, create a key name with the subsequent number, in this case, 2. See the following articles:
I have installed the latest Bot Agent and am currently on Automation 360. However, I ignored the browser extension pop-up dialog box. What do I do?
If you updated the Bot Agent when you launched a browser, you will be prompted to add or remove the Manifest V3 extension through a pop-up dialog box. To enable the Manifest V3 extension, you must select the Add Extension option. If you ignore the pop-up dialog box, the Manifest V3 extension is disabled. To enable the extension and apply the group policy, you must restart your browser.
What is the Automation 360 started debugging this browser pop-up message and how do I disable it?
Google Chrome displays the Automation 360 started debugging this browser pop-up message for the Browser > Run JavaScript or for the inline JavaScript click action. Google has restricted software providers to add JavaScript in the page content that restricts execution of any inline JavaScript click. In Manifest V3, Google has updated the security to ensure that the Google Chrome browser is not compromised.
You can disable the message by creating a new registry with Data value as browser extension ID. See A360 | Getting pop-up while running the bots "Automation 360" started debugging this browser.