YEs -this worked for me! Thanks for the tip!
I was also facing the similar situation where every time when we run the workflow getting the UiPath extension issue although it is installed. Every time we install and run it got corrupted. The actual issue was I am using Kill activity to close the unwanted chrome browser window this was causing the chrome extension got corrupted.
Just update the uipath.automation.activities from the manage packages and it will work âŚhope this helped u
Hi Nissy Ruth,
Can you provide us the version ID ?
I faced the similar issue on version 22.4.6.
Thanks in advance,
Nikos
Hi thanks, the issue was resolved
I see the issue was resolved but the solutions in here did not work for my use case.
I created a workflow in my development environment, tested the workflow and it was working as expected, so I transferred it into the Test environment to run every 3 hours for 7 days. Every single run was successful but as soon as I transferred the workflow to my Production machine, I kept getting error "Could not communicate with the UiPath extension for browser âchrome.exeâ. Please make sure the extension is installed and enabled.
We contacted UiPath technical team, got on a call with them, they were not exactly sure what was wrong either and were not of much help.
What did help though was adding a 3 second delay in my workflow right before the bot opens chrome and attaches to the browser using âUse Application/Browserâ activity. For some reason, that seems to have fixed my issue.
I wanted to add this to the list of solutions provided in this forum, incase someone else runs into a similar situation and this might help them
Hope yâall have a wonderful day!
Also forgot to mention that I had chrome extension already installed and enabled in the Production Machine. Thatâs why just adding a 3 second delay before the Use Application/Browser worked without changing anything else
I have the similar issue in unattended run using firefox. Tried out all the solutions mentioned here and also tried using firefox 32 bit. Please helpâŚ
Thanks in advance
There is a known issue with some older UiAutomation Activities prior to version 21.2.
After some recent updates Chrome browser may take longer to start, especially if there is increase cpu activity on a machine. There is no timeout in Open browser activity and this was handled as browser extension error in mentioned older activities.
The browser start handling was improved on latest UiAutomation package releases. Update your packages to latest version.
How is that even an answer ? You want them to entirely rework on the process in a different browser and spend whole lot of time.
I have developed a blank process and published the process into Orchestrator. While publishing it asked me to provide the URL, I have given the local documents folder as URL where my nupkg process was saved. When I ran the process through Orchestrator, it has thrown same error âCannot communicate with Browserâ. None of the solutions provided here worked. I have tried by clicking Allow access to file URLs in extensions and it worked for me.
I solved this problem by closing all other chrome profiles and leaving the profile that I will use as automation, after I checked successfully, I could open other chrome profiles again.
Donât forget to restart UiPath studio and assistant, also donât forget to also check that the UiPath extension in your browser has obtained access rights.
The issue with firefox extension was resolved following the solution as described here
I have tried, but it persists. I am now seeking help and would appreciate any assistance from someone who has fixed a similar issue before. Thank you in advance for your help.
Despite my efforts, I am still encountering the following error message:
Cannot communicate with UiPath Platform
The native part of the extension is not configured correctly.
Re-install the extension from UiPath Studio.
Just leaving a solution for people who may meet this same problem:
1.Opening the extension of the Chrome:
2.Turning the right bottom button âonâ