Retry hierarchy on kAXErrorInvalidUIElement#3003
Draft
Fishbowler wants to merge 1 commit intomainfrom
Draft
Conversation
Fishbowler
force-pushed
the
fix_kAXErrorInvalidUIElement
branch
from
e28bbf0 to
21d4d72
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Originally: dincozdemir@f1edd5d
Proposed changes
Imported from a fork.
kAXErrorInvalidUIElement errors occur when elements are removed in the missing of an XCTest operation. It's rare, but common enough that I've seen it pop up in the community Slack a bunch of times, and even in Maestro Cloud runs.
Testing
tbc
Issues fixed
#2617