-
-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Appium Inspector Desktop vs Accessbility Inspector Mac #19768
Comments
https://github.com/appium/WebDriverAgent (behind XCUITest driver) generates the XML tree, but basically the information comes from Apple's XCTest framework. So potentially the XCTest framework and accessibility may return different result. (Only Apple knows of the details) Btw, what's the result of |
Here, so is it safe to assume, Accessibility Inspector might not use the XCTest Framework and has other API's available for it?
|
Yes.
Do you mean via appium? Then no. Appium depends on XCTest framework. For RN, setting |
Closing this ticket as of now... But I think it would be better if WebDriverAgent gets as close to Accessibility Inspector to identify and interact with elements. |
Just as a note, selecting elements through the Inspector screenshot is not guaranteed to find exactly the element you need, because there may always be some overlap. I would advise updating Inspector to the latest version and then referring to the documentation: for example, the element handles toggle could be useful here: https://appium.github.io/appium-inspector/latest/session-inspector/screenshot/#element-handles-toggle |
Hi, so I've an app developed in React native. In the below screenshots you can see that the
Wings
option in Accessibility Inspector is properly identified but by Appium Inspector it is not.As of my understanding, XCUITest Driver generates the accessibility tree right? So does Accessibility Inspector not use the same?
The text was updated successfully, but these errors were encountered: