Following the browser/Chromium application update, why is it no longer possible to identify web elements using Active Accessibility (AA) mode with UIAutomation activities?
Issue Description:
Following the browser/chromium application update to version 114.0.1823.37, it is no longer possible to identify web elements using Active Accessibility (AA) mode for both Classic and Modern UIAutomation activities.
The problem occurs regardless of the UIAutomation package Major version or the Studio version.
This has been observed with Chrome, Edge, as well as other Chromium-based applications such as the Citrix Workspace UI.
Available Workarounds:
- Upgrade the UiPath.UiAutomation.Activities package in the project to a patched as soon as possible.
The following Broken selectors after Chrome/Edge update to version 114.0.1823.37 will be updated as patches for the LTS versions of the UiPath.UiAutomation.Activities packages are released.
Or
- Revert to Chrome / Edge version 113.
Next Steps:
After updating to a supported LTS patch version of UiPath.UiAutomation.Activities package, if the issue is still occurring and if reverting to the previous version of Chrome / Edge is not possible, contact UiPath Technical Support team with the following details:
- Steps that have been taken in an attempt to resolve the issue
- The current version of Chrome and/or the Chromium application where the issue is occurring.
- The current version of the UiAutomation.Activities package being used in the process.
- A screenshot of the current selector that is breaking.
- Robot Execution logs and/or Studio logs after causing the issue to occur.