- 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
- Citrix Technologies Automation
- 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
Troubleshooting
This page presents the most frequent reasons for which the UiPath Extension for Chrome might not work properly, and how to solve these issues.
- In Google Chrome, navigate to
chrome://extensions/. - Make sure the extension is installed and enabled, as explained here.
- If the extension was installed correctly but does not appear in Chrome, check if there are Group Policies that affect the
extension, as explained here.
Note: Selecting the Developer mode check box at the top of the
chrome://extensions/page displays the Update button on the extension Details page.
ChromeNativeMessaging.exe enables communication between the UiPath
Extension for Chrome and the UiPath Studio/Robot.
- Open Chrome.
- Open Task Manager.
- Check if the
ChromeNativeMessaging.exeprocess is running.
- If the process is not running:
- Make sure the extension is installed. For more information, check the installation methods described in the Extension for Chrome page.
- Check if there are Group Policies
affecting
ChromeNativeMessaging.exe. See Group Policies for more information. - Check if ComSpec variable is defined correctly.
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 Google Chrome 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 Incognito Mode. To enable these:
- In Google Chrome, navigate to
chrome://extensions/. The Chrome Extensions page is displayed. - Navigate to the UiPath Web Automation extension and click the Details button. The UiPath Web Automation details page is displayed.
- Make sure the Allow in incognito and Allow access to file URLs options are selected.
UiPath Extension for Chrome does not support automating multiple browser instances running with multiple user profiles at the same time. As such, browser automation requires you to close all active instances of Chrome and restart the browser using a single user profile.
In some cases, Chrome background processes prevent it from closing completely, which interferes with automations even if the browser instance is not visible.
We recommend closing Chrome by right-clicking the Chrome icon in the System Tray, and selecting Exit. This ensures that no other user profiles remain in use in the background.
When installing the UiPath extension for Chrome 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 or using Chrome Cloud Policies.
Because the machine level has priority, the extensions set at the user/cloud level are uninstalled.
chrome://policy if this warning is
displayed under ExtensionInstallForcelist:
This policy is working as intended but a conflicting value is set elsewhere
and is overridden by this policy.
- Install the UiPath extension
for Chrome using the
NativeHostOnlyinstallation 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 addCHROME_INSTALL_TYPE=NativeHostOnlyto the installation command for UiPathStudio.msi. Example:UiPathStudio.msi ADDLOCAL=DesktopFeature,Studio,Robot,RegisterService,ChromeExtension CHROME_INSTALL_TYPE=NativeHostOnly. - In the ExtensionInstallForceList policy,
add the value:
-
For the Group Policy Online installation method (that installs the Chrome Web Store extension):
kmejkhcmhgilmppjodlgaklnmdmmhhcl;https://clients2.google.com/service/update2/crx -
For the Group Policy Offline installation method (that installs the self-hosted extension):
ndmegdjihnhfmljjoaiimbipfhodnbgf;file:///C:/ProgramData/UiPath/UiPath.Common/ChromeExtension_SelfHosted/extension_manifest_chrome.xml
-
- 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.
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 Chrome v22.4 will not work at all with this restriction. Please consider upgrading to the v22.10 of the extension available with UiPathStudio.msi 2022.4.4.
- The UiPath Extension for Chrome v22.10 will be restricting to working with LTS versions of UiAutomation (19.10.x, 20.10.x, 21.10.x, 22.4.x)
- The
InjectJSActivity will not work.
2
then:
- All the limitations from
DeveloperToolsAvailability=0apply - The
ChromiumAPIinput 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.
This property is available starting with UiPath.UIAutomation.Activities v22.12.0-preview.
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 Chrome 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 Incognito mode
- Multiple browser profiles
- Multiple Chrome instances with multiple user profiles
- Stopping all Chrome 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
