Jonathan Lipps

And there are some apps (like games for example) that only expose basic container elements, whereas all the user-interactable elements are opaque to the accessibility system (and therefore Appium). so...

you probably need to adjust the way you are using accessibility in your react native app. it may be hiding all the internal elements. i know @wswebcreation has written some...

I think this is a known issue. Maybe @stuartbrussell-intuit can comment?

this looks like an upstream bug in webdriverio: https://github.com/webdriverio/webdriverio/issues/8523 but in any case the functionality is deprecated so you probably want to find a different strategy (stopping/starting the session again...

and we should probably remove this action entirely from the inspector

I guess the inspector code samples are a bit out of date. No one is really on top of maintaining them whenever there are updates to the corresponding client libraries....

You'll need to be more specific about what's going wrong for us to be able to help.

it would still be worth exploring the strategy of using the official context API. if that works sensibly, it will be a much better user experience.

You're probably right. I was thinking of something simple like a wrapper around the existing functionality that simply adds a new context to the list and handles the case of...

The Selenium project recommends not using XPath selectors in WebDriver code. The object you're inspecting has an ID--why not use that?