XPath as a locator coming in recorded script about appium-inspector HOT 4 CLOSED

Assuming this is an Android hybrid app, this makes sense, as the id locator strategy is not part of the W3C spec. Chrome runs in W3C mode by default, so it will only work with the available W3C strategies, of which the only one here is xpath.
However, you can disable Chrome's W3C mode, and the recorder will then be able to use other strategies. You can do this by starting the Inspector session with the "appium:chromeOptions": {"w3c": false} capability.
Check the UiAutomator2 web context capabilities for more info.

from appium-inspector.

Thank you! "appium:chromeOptions": {"w3c": false} is working.

from appium-inspector.

This depends entirely on the suggested locators generated for your element. If the Inspector only generates XPath - that is what the Recorder will use. If the element has a unique ID and the Inspector suggests that, then the Recorder will pick that:

from appium-inspector.

The elements has unique IDs available, but still it uses the XPath.

Note: I am running it for hybrid application.

from appium-inspector.