Does anyone have a workaround for this error in chrome? it is a known issue, UiPath is aware of the issue but there is no timeline of when it will be fixed.
I am trying to check if the checkbox is ticked, the get attribute activity gives the aforementioned error. I tried find children,get text, get visable text but the way checkbox is written makes it impossible:
@DVM, if you are using Find Children activity and in between page DOM structure is modified then UiPath will throw an error.
Instead you can have a local array or list of all IDs (or any other unique reference) of all check boxes that are to be checked. And then loop through this collection to generate a dynamic selector and use check activity.
Don’t think the selector is the issue here, as mentioned “Get Attribute” works perfectly in IE but there is a bug in chrome that gives this error.
The attribute that I am trying to find as a workaround for “Get Attribute” not working in chrome is highlighted in red, but UiPath is not able to match it in the UiExpolorer
I’m still curious to see the selector of exact “GetAttribute” activity you used.
Othewise, can you please try to use below simple selector for “GetAttribute” activity and check the value of “checked”?
webctrl id=“consentsList|1@isSelected” type=“checkbox”
@DVM here we do see that the children filter is failing
Check the selector and if its not a direct child then change find children property scope to FIND_DESCENDANTS
I would suggest to retrieve the selector to the check box via uiexplorer, manually navigating in the Visual tree and right click set as target element
It seems to me that problem comes from wrong check box selector and not from a chrome bug. Another option to test is to do a click activity in a separate xaml to the check box (alternate type into space to the checkbox)
Tried FIND_DESCENDANTS gives the same 3 elements as shown in the screenshot.
As mentioned before the same selector works like a charm in IE, if you click the link in the description it shows a thread where uipath officially responds that they are aware of the issue and that there is no timeline on when it will be fixed.
I came up with a workaround using chrome dev tool where I copy the selector from the dev tool and do regex on “title” value. so far works like a charm, if you guys have any feedback I would of course appreciate it.