- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Edge extension troubleshooting
This page presents the most frequent reasons for which the extension for Edge might not work properly, and how to solve these issues.
ChromeNativeMessaging.exe
enables communication between the UiPath Extension for Edge and the UiPath Studio/Robot.
- Open Microsoft Edge.
- Open Task Manager.
- Check if the
ChromeNativeMessaging.exe
process is running. -
If the process is not running:
ChromeNativeMessaging.exe
process runs under the current user
and it uses cmd.exe
to start the browser.
ComSpec
environment variable is missing or has an invalid
value, then Microsoft Edge cannot launch the
ChromeNativeMessaging.exe
.
Furthermore, the administrator may disable the command prompt for some users or configure it to always run with elevated privileges.
ComSpec
environment variable.
This variable is set at Windows installation and must be set to:
%SystemRoot%\system32\cmd.exe
.
ComSpec
environment variable is set correctly but the problem
persists, the user may not have permission to run the command prompt. In this case,
the ChromeNativeMessaging.exe
process cannot be started with
cmd.exe
running under the current user.
NativeHostsExecutablesLaunchDirectly
Group Policy allows admins to turn this on for users in
restricted environments (Cloud PCs that forbid cmd.exe
, for
example).
By default, the extension is not granted access to File URLs or InPrivate mode. To enable these:
- In Microsoft Edge, navigate to
edge://extensions/
. The Microsoft Edge Extensions page is displayed. - Navigate to the UiPath Browser Automation extension and click the Details button.
- Make sure the Allow in InPrivate and
Allow access to file URLs options are selected.
UiPath Extension for Microsoft Edge does not support automating multiple browser instances running with multiple user profiles at the same time. Therefore, browser automation requires you to close all active instances of Microsoft Edge and restart the browser using a single user profile.
In some cases, Microsoft Edge background processes prevent it from closing completely, which interferes with automations even if the browser instance is not visible.
We recommend closing Microsoft Edge by right-clicking the Microsoft Edge icon in the System Tray, and selecting Close Microsoft Edge. This ensures that no other user profiles remain in use in the background.
When installing the UiPath extension for Edge using Group Policy the ExtensionInstallForcelist is updated at the machine level.
This can cause a conflict if the ExtensionInstallForcelist is also defined at the user level.
Because the machine level has priority, the extensions set at the user/cloud level are uninstalled.
edge://policy
if this warning is displayed
under ExtensionInstallForcelist:
More than one source with conflicting values is present for this
policy!
- Install the UiPath extension
for Edge using the
NativeHostOnly
installation method.This installation method enables communication between the extension and Studio/Robot.
It does not make any changes to the Group Policies.
To use this installation method addEDGE_INSTALL_TYPE=NativeHostOnly
to the installation command for UiPathStudio.msi. Example:UiPathStudio.msi ADDLOCAL=DesktopFeature,Studio,Robot,RegisterService,EdgeExtension EDGE_INSTALL_TYPE=NativeHostOnly
. - In the ExtensionInstallForcelist policy, add the
value:
- For the Group
Policy Online installation method (that installs the
extension from Microsoft Edge Add-ons Store):
dknkgjgkdpkmddgdjlgdhfojlaehikmk;https://edge.microsoft.com/extensionwebstorebase/v1/crx
- For the Group
Policy Offline installation method (that installs the
self-hosted extension):
ndmegdjihnhfmljjoaiimbipfhodnbgf;file:///C:/ProgramData/UiPath/UiPath.Common/EdgeExtension_SelfHosted/extension_manifest_edge.xml
- For the Group
Policy Online installation method (that installs the
extension from Microsoft Edge Add-ons Store):
- In the NativeMessagingAllowlist policy, add the value:
com.uipath.chromenativemsg_v2
. - Set DeveloperToolsAvailability Group Policy to the
value
1
(Allow usage of the Developer Tools).This setting is required to enable the full extension functionality.
Simulate
input method no longer works on HTML elements that
have a click handler with javascript:
URI.
In this case, the simulated click will not take effect and no errors will reported.
This was reported as a Chromium bug. This issue is quite rare as very few HTML elements have click handlers in this form.
Workarounds
Two workarounds are available for this issue:
- Identify the failing Click activity in your workflow and change the input method from Simulate to any other input method (Chromium API, Hardware Events, Window Messages).
- Upgrade to UiPath.UIAutomation.Activities package v22.12 or newer and use the Enable workaround for simulate click with MV3 extension option in Project Settings.
The DeveloperToolsAvailability has the following possible values:
- 0 = Disallow usage of the Developer Tools on extensions installed by enterprise policy, allow usage of the Developer Tools in other contexts
- 1 = Allow usage of the Developer Tools
- 2 = Disallow usage of the Developer Tools
1
to
enable the full functionality of the extension.
This value is automatically set correctly when the extension is installed 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.
0
then:
- The UiPath Extension for Edge will be restricting to working with LTS versions of UiAutomation (19.10.x, 20.10.x, 21.10.x, 22.4.x)
- The
InjectJS
Activity will not work.
2
then:
- All the limitations from
DeveloperToolsAvailability=0
apply - The
ChromiumAPI
input method will not work.
ChromeNativeMessaging.exe
could not
be started:
Cannot communicate with UiPath Platform
The native part of the extension is not configured correctly.
Re-install the extension from UiPath Studio.
jQuery $
, or to interact with page code (e.g.,
window.alert
). The Inject Js Script activity won't
report an error, but the script will fail to execute and the following error will be
reported in the browser DevTools (F12): "Refused to execute inline script because it
violates the following Content Security Policy directive."
This is a limitation introduced by the MV3 platform.
To fix this issue, select the Execution world - Page option from the Inject Js Script activity.
Your existing JavaScript code doesn't require any changes, and by using the Execution world - Page option it will work for both MV2 and MV3 extensions.
For MV3 extensions, the browser loads the extension later, after the web pages have loaded. This means that on slower machines, the Open Browser activity from UiPath.UiAutomation.Activities version 22.10 or older can reach the internal timeout of 20 seconds before the extension has started.
Starting with v22.12.0-preview, the internal timeout for the Open Browser activity has been increased from 20 seconds to 60 seconds.
Since you may need to set a longer timeout for the browser startup, it is now configurable from the Use Application/Browser and Open Browser activities. The following project settings have been added:
-
UI Automation Classic → Browser → Open browser timeout (seconds)
-
UI Automation Modern → Application/Browser → Open browser timeout (seconds)
UIPATH_OPEN_BROWSER_TIMEOUT_SECONDS
environment variable. For
example, set UIPATH_OPEN_BROWSER_TIMEOUT_SECONDS=120
to use 120
seconds for the activity's timeout.
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Description
- Solution
- Other workarounds
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Multiple Microsoft Edge instances with multiple user profiles
- Stopping all Microsoft Edge instances
- Group Policy conflict
- Description
- Solution
- Known issues specific to MV3 extensions
- Click activity with Simulate fails on specific web page elements
- The DeveloperToolsAvailability Group Policy value must be set to 1
- The UiPath Web Automation browser window shows a warning
- The Inject Js Script activity can no longer be used to access page variables and code
- Open Browser activity has an insufficient timeout