Currently, Studio is using version 24.10.12, and the extension is also using version 24.10.
The extension is installed via Group Policy (offline), and the DeveloperToolsAvailability is set to 2.
Additionally, UiPath.UIAutomation.Activities is using version 24.10.12.
There are plans for approximately 140 terminals to be upgraded to version 149 or later, and we are considering how to respond from a maintenance perspective.
Since the terminals running the RPA are not our own, we cannot change terminal-specific settings such as the registry, and we believe that upgrading the extension to version 26.10 is the fastest course of action.
(This is because we are also planning to upgrade the UiPath version to 25.10.xx separately.)
As a test, I set up the same environment on our own terminals and ran the demo project. I found that the version 24.10.xx of UiPath.UIAutomation.Activities works, but with version 25.10.xx, it gives the error “Cannot communicate with the browser. Please check the UiPath extension.”
The following site states, [UIAutomation will no longer function properly after 24.10.], and it is unclear whether this has been verified.
Impact on UiPath extensions installed via Group Policy in Chrome/Edge v149
How can we reproduce the issue in the current environment?
(I would like to create documentation showing that an issue occurs with the extension at version 24.10 and does not occur when upgraded to 26.10 to obtain approval for the upgrade process.)