-
-
Notifications
You must be signed in to change notification settings - Fork 6.1k
-
-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
XCUITest Element could not be found error #7009
Comments
Hello! I just started to test a chain appium 1.6 with ios 10 test (I had working tests with appium 1.5 and ios 9.3). I've got an issue that appium can't interact with elements in a tree with XCUIElementTypeOther. It can't find an element using xpath or accessibility id or click on it. |
I'm getting the same issue: How does one find the new elements with out the Inspector tool which is not available in 1.6.0-beta3 ? |
@srkannan for the time being, use the page source command |
@jlipps I am unable to locate element appears on a video , though it has Accessibility ID , Label and Type provided. Please help. |
Noticed the same problem with XCUIElementTypeOther myself, also. Perhaps, it will help if we could modify the issue title to include the word "XCUIElementTypeOther"? |
The UI tree generated by XCTest is different from the one generated by instruments. So don't expect same paths or class names to work for both frameworks. Most of the times it is necessary to update locators according to the actual tree. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hi
Before XCUITest (Before IOS 10)
I was using below method to find a UI Element in IOS application:
But after changing implementation to XCUITest it gives the below error. Does anyone know how can I fix that?
And this is the driver.getPageSource() output of the current Screen:
https://drive.google.com/file/d/0B3eSt3_PT8YXakQwRC1ZOHFDT2c/view?usp=sharing
Thanks
The text was updated successfully, but these errors were encountered: