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
iOS App crashes in during getPageSource() if it has large page source - Error getting main window -25215 #13864
Comments
This error is thrown by XCTest and we cannot do anything about it in Appium. Consider reporting the issue to Apple. You could try #13595 (comment) as a workaround to get the page source. |
@sundarsiv1995 you can also try using "Accessibility Inspector" from xCode with this screen (if you need to inspect it) |
@mykola-mokhnach |
Tried adding useJSONSource and snapshotTimeout capability in appium inspector. [WD Proxy] Matched '/source?format=json' to command name 'getPageSource' |
@amedvedjev Tried with accessibility inspector. But not getting any properties for that PDF pages. But I am able to get the name, label for the other native buttons present in the screen. |
Unfortunately there is nothing we can do there from Appium side. Consider reporting the issue to Apple. Closed as third party issue |
When I am trying to inspect a app screen which has a PDF document with 21 pages displayed, the app crashes with the below error in appium logs.
[Xcode] 2020-01-09 12:38:52.554368+0530 WebDriverAgentRunner-Runner[423:16389] Internal error: Error Domain=com.apple.dt.xctest.automation-support.error Code=8 "Error getting main window -25215" UserInfo={NSLocalizedDescription=Error getting main window -25215}
[Xcode]
[Xcode] t = 2647.09s Snapshot accessibility hierarchy for app with pid 431
[Xcode]
[Xcode] t = 2647.10s Snapshot accessibility hierarchy for app with pid 431
Note: The app has another screen where PDF is displayed which has only one page. I am able to inspect this page.
Solutions tried:
1.Tried with 1.16 beta version of appium
2.Checked if it is webview. Not a webview.
Please help here.
The text was updated successfully, but these errors were encountered: