Raising on behalf of Leonid from Waze, as he's not able to access the portal right now.

Requested Support -

It seems xpath 2.0 is not supported when searching elements via the Search field of the Automation tab. (open device -> open Automation panel on the right).

Currently, for Android (UiAutomator2) we are using expressions that are not supported by XPath 1.0.
Example: //*[ends-with(@resource-id, ':id/routeViaText')]

Test development and debugging would be much easier if our existing XPath locators were supported by your inspector tool. We are able to execute scripts on the Cloud with these XPaths and using Appium 2, but if we search using these XPaths to identify elements, it doesn't work.

Comments

  • Hi Chinni,
    I've set this idea as a candidate, and regardless, I'll start investigating it and try to push it for Q3.