The adoption of Manifest V3 represents one of the biggest shifts in the Google Chrome extensions platform since it launched a decade ago. Extensions using Manifest V3 will enjoy enhancements in security, privacy, and performance.
We’ve implemented a completely new extension following the Manifest V3 standard released by Google. This new extension can be installed from both Studio ->Tools->UiPath Extensions panel as well as Command Line as described in the documentation.
After the initial release of the UiPath Chrome Manifest V3 Extension with Studio version 2022.4, we recently released patches containing MV3 Extensions for both Chrome and Edge to all UiPath Studio LTS versions: 2022.4.4, 2021.10.8, 2020.10.14, and 2019.10.9.
All these UiPath Studio patches are using the 22.10.5 version of the extensions.
More information is available in the online documentation on Extensions for Chrome and Edge.
For further guidance regarding the UiPath MV3 transition you can also check the FAQ section at the end of this forum post.
Chrome Manifest V2 official support from Google ends in January 2023 . After this point in time, all MV2 extensions will cease to function in Chrome ( limited enterprise exceptions ).
June 2023 will be the deadline for when MV2 extensions will no longer function in Chrome even with the use of enterprise policy.
We highly recommend that you upgrade and start using the new MV3 extensions with your automation processes before the deadline.
The migration options for this change:
• If you are on a supported version, apply the corresponding UiPath Studio patch or upgrade to the latest Studio release.
• If you are on an unsupported version, upgrade to the latest patch of a supported version of UiPath Studio.
• If you are already using the 2022.4 release that include the MV3 extension for Chrome, apply the latest 2022.4 patch to be able to use the MV3 extension for Edge as well.
The only notable difference from a user perspective is the presence of the following popup in Chrome, when the UiPath MV3 extension was not installed by policy.
This is normal behavior as the UIPath MV3 extension is using DebuggerAPi .
This was reported as a Chromium bug here: Chrome Issue.
- For UiAutomation 21.10 & newer, use of Chromium API input method instead of Simulate is required.
- For UiAutomation older than 21.10, use of Hardware Events input method instead of Simulate is required.
The DeveloperToolsAvailability Group Policy value should be set to 1 (Allow usage of the Developer Tools) to enable the full functionality of the extension.
This value is automatically set correctly when the extension is installed using Group Policy, but it will be overwritten if your system administrator has set another value for this policy.
The other values for DeveloperToolsAvailability cause the problems listed below.
If DeveloperToolsAvailability=0 (Disallow usage of the Developer Tools on extensions installed by enterprise policy) then:
- The 22.4 MV3 extension will be completely broken because it cannot load the Driver code
- The 22.10 MV3 extension will be limited to working with the embedded LTS driver packages (19.10, 20.10, 21.10, etc).
- The InjectJS activity will not work.
If DeveloperToolsAvailability=2 (Disallow usage of the Developer Tools) then:
- All the limitations from DeveloperToolsAvailability=0 apply
- The ChromiumAPI input method will not work.
What happens if I do not upgrade to the UiPath MV3 extensions before the January 2023 deadline for the MV2 sunset? According to the timelines published by Chrome and Edge all existing MV2 extensions will stop working in January 2023. This deadline can be extended to June 2023 by installing the MV2 extensions using the ExtensionInstallForceList Group Policy.
This means that the automation processes that rely on the UiPath MV2 extensions will stop working after the deadline for MV2 sunset.
We strongly recommend that you upgrade to the UiPath MV3 extensions before the deadline.
Do I need to make any changes to my automation processes after upgrading to the UiPath MV3 extensions?
No changes are required to your existing automation processes.
The UiPath MV3 extensions are backwards compatible with all existing UiPath.UIAutomation.Activities packages.
Yes, the “Inject JS” activity will continue to work with the UiPath MV3 extensions.
No, the UiPath Orchestrator does not need to be upgraded.
Yes, there is a known issue that is specific to MV3 extensions.
In this case, the simulated click will not take effect and no errors will be reported.
This issue is quite rare as very few buttons have click handlers in this form.
If you encounter this issue, then you must update your workflow and change the input method for the failing Click activity from “Simulate” to “ChromiumAPI”, “Hardware Events” or “Window Messages”.
The UiPath MV3 extension for Chrome can only be installed if the Chrome version is 98 or greater. You can check the Chrome version by opening chrome://settings/help in Chrome.
UiPathStudio.msi will also check the Chrome version and automatically install the appropriate UiPath extension (MV2 or MV3).
The UiPath MV3 extension for Edge can only be installed if the Edge version is 98 or greater.
You can check the Edge version by opening edge://settings/help in Edge.
UiPathStudio.msi will also check the Edge version and automatically install the appropriate UiPath extension (MV2 or MV3).
UiPathStudio.msi 2022.4.1 includes the MV3 extension for Chrome. UiPathStudio.msi version 2022.4.4 added the MV3 extension for Edge. This means that if you are using the Edge extension in your automation processes you will need to apply the latest UiPathStudio.msi patch.
If you are using UiPath in an air gapped environment and continue to use Chrome versions released prior to January 2023, the MV3 restriction will not be enforced and there will be no impact.
Once you update Chrome to a version released after January 2023, the MV3 restriction will apply and UiPath Chrome extension update is needed.
Please share your feedback, as well as any questions that might arise!