This page presents the most frequent reasons for which the UiPath Extension for Chrome might not work properly, and how to solve these issues.

Check if the Extension for Chrome is installed and enabled

1. In Google Chrome, navigate to chrome://extensions/.
2. Make sure the extension is installed and enabled, as explained here.
3. 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.

Check if ChromeNativeMessaging.exe is running

1. Open Chrome.
2. Open Task Manager.
3. Check if the ChromeNativeMessaging.exe process is running.

4. If the process is not running:

• Make sure the extension is installed. For more information on how to install it, check the docs page.
• Check if there are Group Policies affecting ChromeNativeMessaging.exe. See the docs page for more information.

Enable access to file URLs and incognito mode

By default, the extension is not granted access to File URLs or Incognito Mode. To enable these:

1. In Google Chrome, navigate to chrome://extensions/. The Chrome Extensions page is displayed.
2. Navigate to the UiPath extension and click the Details button. The UiPath Chrome extension details page is displayed.
3. Make sure the Allow in incognito and Allow access to file URLs options are selected.

Multiple browser profiles

Multiple Chrome instances with multiple user profiles

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.

Stopping all Chrome instances

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.

Check if ComSpec variable is defined correctly

If the UiPath Extension for Google Chrome cannot launch the ChromeNativeMessaging.exe, the solution is to manually add the ComSpec environment variable.

This variable is set at Windows install and should have the value %SystemRoot%\system32\cmd.exe.

Known issues specific to MV3 extensions

Click activity with Simulate fails on specific web page elements

The Click activity with the Simulate input method no longer works on HTML buttons 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 here: https://bugs.chromium.org/p/chromium/issues/detail?id=1299742
This issue is quite rare as very few buttons have click handlers in this form.

Workaround
Change the input method for the failing Click activity from Simulate to any other input method:

• Chromium API
• Hardware Events
• Window Messages

The DeveloperToolsAvailability Group Policy value must be set to 1

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.