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
UiAutomator2 StackOverflow in AccessibilityNodeInfoHelpers.getVisibleBounds #12892
Comments
I can apply the patch, but it would be interesting to know what prevents you from creating a PR? |
I am still not fluid in git, should I create a pull request? |
it worth trying. Simply fork the project, create a branch there, push your changes and there will be a big green button in GitHub to create a PR. Give it a proper title and description and click |
Alright, I created that pull request |
Cool, added comments |
The fix has been published in appium@beta. |
The problem
When automating certain screens result in an StackOverflowException when getting the AccessibilityNodeInfoHelpers.getVisibleBounds. This is called when getting the UiAutomationElement attributes.
This is also happening when inspecting the app with Appium Desktop Inspector, which results in Appium Desktop loading forever.
I only experience this with UIAutomator2 but UIAutomator1 is working fine.
This bug is similar to #12545 only at a different place.
Again this looks like an application issue but it would be good if UIAutomator2 could catch and handle it.
Environment
Link to Appium logs
UiAutomator2StackOverflowException.log
Suggested Fix
Here how I quickly fixed it similar to the resolution of #12545 -> Avoid stack overlow exception by limiting the maximum recursion depth:
UiAutomator2StackOverflow.patch
The text was updated successfully, but these errors were encountered: