Hello, all our automations are using InPrivate mode for Edge interactions so massive impact in our side . Please provide update as soon as issue is solved.
I tried to install UiPath MV2 extension by adding the extensionID to the ExtensionInstallForceList but i canno’t check allow in private because it doesn’t show extension after changing this.
Last manual workaround is to launch robots manually and when edge is opened in InPrivate, i launch edge again to launch the “ChromeNativeMessagingHost.exe” and then it can work. This is a very short term workaround because we have more than 40 running.
We are sorry for any inconvenience this issue may have caused. Unfortunately we have no updates, but we will write here when we have news.
I understand you have tried to install the UiPath MV2 extension, but it didn’t work.
Please make sure you have added the correct value to the ExtensionInstallForcelist policy (corresponding to the Group Policy Online installation): bhchaenngmlcobfechfkikaofjlmejop;https://edge.microsoft.com/extensionwebstorebase/v1/crx
After this change, you can restart the browser and you should be able to see this extension and set the “Allow in InPrivate” option for it.
We have tested this solution and other customers also have confirmed that it worked for them.
I am also facing the same issue. But I have observed is when I updated the UiPath Studio/Edge extension to 2023.4 then only I started getting an InPrivate mode “Can not communicate with the browser” error.
So, I Uninstalled UiPath studio and extension and reinstall 2021.10 with the same version extension, and It started working.
(NOTE: Edge Version 115. 0.1901.203 (Official Build) (64-bit))
My Question here is, If I install 2023.4 studio and keep the 2021.10 edge extension will it work, or is it good practice to keep the studio version higher and the extension version lower??
Please suggest as we have planned for the upgrade to latest version from this month.
we are trying to implement workaround #3. Edge group policy has been updated to bhchaenngmlcobfechfkikaofjlmejop
But the extension is not installed even after restart of the computer.
What shout we do to get the extension installed?
Thanks for any guidance!
After you updated Studio to version 2023.4, the MV3 extension for Edge was installed. You started getting the error for starting browser with InPrivate option because it only appears for MV3 extensions.
When you reverted to Studio version 2021.10, you probably used an installer with a version lower than 2021.10.8, which installs the MV2 extension for Edge.
You can install Studio 2023.4 and use the MV2 extension for Edge until this issue is resolved. For workaround #3 we recommended the installation of the extension with the ID bhchaenngmlcobfechfkikaofjlmejop, which is the latest version of the MV2 UiPath extension for Edge.
The best practice is to use the browser extension that comes with the latest version of Studio. But for specific cases like this, you may need to use lower version of the extension.
I tried to install Studio 2023.4 and uncheck the extension for Edge by navigating to the advanced setting option to keep a lower version extension(i.e. v2021.10) as it is but it is removing the existing Edge extension(i.e. V2021.10) from the browser.
so I tried to search for the extension UiPath Browser Automation 21.10 but I am unable to find it.
so, my question here is, Is there any way to install an extension (UiPath Browser Automation 21.10) or can you provide steps on how to download and install UiPath Browser Automation 21.10
I don’t know if you have seen the update from August 30th, in the original post, regarding the workaround implemented with UiPath.UIAutomation.Activities package version 23.8.0-preview. If you use this package dependency in your projects, you can continue working with the MV3 Edge extension version 23.4.
But if you still have other projects using lower versions of the UIAutomation package, and you want to use the MV2 extension, it is not enough to install the extension directly from the web store. You also need to ensure the native part of the extension (ChromeNativeMessaging.exe) is configured correctly. That’s why it is recommended to install the extension from UiPath Studio.
In this case, you can use these steps:
Install Studio 23.4 and the Edge extension 23.4 (from the installer, or from Studio after installation).
Install the MV2 extension by adding the bhchaenngmlcobfechfkikaofjlmejop extension ID of the 22.4 Edge extension (MV2) to the ExtensionInstallForcelist Group Policy, like this: bhchaenngmlcobfechfkikaofjlmejop;https://edge.microsoft.com/extensionwebstorebase/v1/crx
If you installed the 23.4 MV3 extension using the Group Policy Offline installation method, you can also keep the ID of the 23.4 MV3 extension in the ExtensionInstallForcelist and just add another String value for the 24.4 MV2 extension. Either method should work.
The workaround with adding the bhchaenngmlcobfechfkikaofjlmejop extension ID to the ExtensionInstallForcelist Group Policy still works. That is the latest MV2 Extension ID for Edge available on Web Store (you can check this List of UiPath extensions for Edge).
I think the problem in your case may be that after the extension update to the new 23.10 version you didn’t reactivate the “Allow in InPrivate” option.
Please verify if “Allow in InPrivate” is checked from edge://extensions/?id=bhchaenngmlcobfechfkikaofjlmejop, and let us know the result.
Besides that, we received an update from Microsoft that this bug has been fixed in Edge v119. As of November 2nd, Edge version 119 is on the Stable Channel and it will be progressively updated for all users. Therefore, once your browser is updated to this version, you will no longer need to use the workaround.