UiAutomation Fails With Edge 115 In Private Mode

News Knowledge Base
1

After upgrading Edge to version 115, the automations fail when the browser is opened in Private mode (Incognito mode).

The latest Microsoft Edge browser update to version 115.0.1901.183 introduced a bug regarding the initialization of MV3 extensions for Edge started "InPrivate" mode.

This issue affects all MV3 extensions, not just the UiPath Extension for Microsoft Edge and it has been reported to Microsoft as an Edge bug and awaiting for their review.

Observed Behavior: When Microsoft Edge browser is started using,

  • The Open Browser activity with Options -> Private property set to True or
  • The Use Application / Browser activity with Options-Browser -> Incognito / private window property set to True the browser is opened, but the following error is displayed: "Cannot communicate with the browser, please check the UiPath extension."

The extension is initialized correctly when a normal Edge tab is opened (the Private option is set to False).

Available Workarounds:

  1. Open a normal Edge browser tab before launching the "InPrivate" browser tab

Disadvantage: Requires changes to the automation projects.

  1. Use a temp custom user data folder for the "Open Browser" activity instead of the "InPrivate" option

This achieves the same effect - cookies can be cleared by deleting the custom user data folder.

Disadvantage: Requires changes to the automation projects.

  1. Install the UiPath MV2 extension

This can be done easily by adding the bhchaenngmlcobfechfkikaofjlmejop extension ID to the ExtensionInstallForcelist Group Policy.

Advantage: No changes are required to the automation projects

Disadvantage: Users will need to manually re-check the option to "Allow in InPrivate" from edge://extensions/?id=bhchaenngmlcobfechfkikaofjlmejop

  1. Downgrade Edge to v114

See instructions here: Microsoft Edge Rollback For Enterprises .


1 Like
2

This issue affects all MV3 extensions, not just the UiPath Extension for Microsoft Edge and it has been reported to Microsoft as an Edge bug and awaiting for their review.

What happened?

3

Hello everyone,

This issue has been fixed in the upcoming Edge v119.
Microsoft has notified us that the original bug has been fixed and our internal testing also confirmed this.

Best regards!

1 Like