Chrome extension is not able to see all Ui elements on screen

Help Studio
, ,
1

When opening a new Chrome instance the UiPath extension is unable to see any Ui elements on internal Chrome pages, such as settings pages. If I use an element exists activity and select the whole page, I can use the Ui explorer to go down the element tree to get to the element I’m looking for. Exiting the Ui explorer will then fix the issue until I open a new Chrome instance, causing the issue again. Does anyone have permanent solution to this? I have tried the following:

  • Reinstalling the Chrome extension

  • Reinstalling UiPath studio

  • Installing the Chrome extension from the Google store, from UiPath studio, and while installing

  • Reinstalling Chrome

  • Checking group policies. I am running the same automation on a dev and a production machine. The production machine is running without issues and the dev machine has the same Chrome group policies as the production machine.

2

@BenRafter

  1. Enable Developer Mode:
  • Open the Chrome browser.
  • Go to the Chrome Extensions page by typing “chrome://extensions” in the address bar.
  • Enable “Developer Mode” using the toggle switch located in the top right corner of the page.
  • Check if the UiPath extension appears and is enabled. If not, click on “Load unpacked” and select the UiPath extension folder (typically located at “C:\Users\AppData\Local\UiPath\app-\UiPath\BrowserExtension”).
  1. Clear Extension Data:
  • Open the Chrome Extensions page (“chrome://extensions”).
  • Locate the UiPath extension and click on “Details.”
  • Scroll down and click on “Extension options.”
  • In the UiPath extension options page, click on “Clear browsing data” and select the appropriate options.
  • Restart Chrome and check if the issue persists.
  1. Check Chrome Policies:
  • Type “chrome://policy” in the Chrome address bar.
  • Check if there are any policies related to extensions that may be impacting the UiPath extension.
  • If policies are set, verify if they are affecting the extension’s behavior. You may need to consult with your IT or system administrator to modify the policies if necessary.
  1. Try Different Chrome Channels:
  • Consider using a different Chrome channel (e.g., Canary, Beta) to see if the issue persists. Sometimes, experimental features or updates in specific Chrome channels can impact the compatibility of extensions.
  1. Contact UiPath Support:
  • If the issue persists, it is recommended to reach out to UiPath support for further assistance. They can provide more specific guidance based on your environment and configuration.
3

Hi @BenRafter

In the UiExplorer, could you try navigating to the settings option in the above ribbon & change the Ui framework ro Active Accessibility? Please let us know if this works.

Best Regards.

4

That didn’t work. I also tried UI automation and turning off Delayed Restore, which also didn’t work.

5

@BenRafter

  1. As I see ui explorer is able to show it in visual tree is it that only for indicating you have this problem?
  2. Once indicated is it working normally when you run the process or does it fail with element not found?
  3. Is this happening to any specific site or all sites?

Cheerd

6

Yes, the problem only occurs when trying to indicate a UI element on a new instance of Chrome. It happens on all sites, and once it is indicated processes will run correctly without issue until closing Chrome, then the issue returns.

7

@BenRafter

Is that a corporate laptop ?

and are the extensions installed at user level or for all users?

also are extensions being loaded or are not saved as per org policy?

cheers

8
  1. Yes it is a company provided laptop
  2. Yes
  3. Yes
9

@BenRafter

As per answers looks like the extension is getting turned off or is restricted from your IT. Can you please check internally about the extension not working as expected

cheers

10

We have, there is a specific program that seems to not always start when trying to use the UiPath Chrome Extension, that being the BrowserBridgePortal.exe. I’m guessing the issue is that this isn’t starting when opening a new Chrome instance.

11

@BenRafter

Can you try using a start process and start this exe

cheers

12

Sorry for late reply, but the solution turned out to be updating our UiPath Studio to the latest version which solved the problem, as we were running on an older version before.

13

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.