Fix stuck XCUITest runner when a popup is shown on the screen #510
Conversation
This file contains 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
sometimes those errors contain a screenshot and that creates unreadable logs
with this option the XCUITest runner is coming into foreground even when there is a popup on the screen when at the time when the runner gets launched
shamanec
approved these changes
Nov 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When a popup (like a permission popup for the camera, notifications, etc) is shown before the XCUITest is started, the XCUITest runner will hang and after 30s we get the error
Failed to background test runner within 30.0s.By adding the option
"__ActivateSuspended": uint64(1),when we launch the XCUITest (like Xcode does), this is not happening anymore.Also, the
Error()method ofNSErrorwas a bit too verbose. In the error that we got here, there is a entryscreenshot-datain theuserInfodictionary, and we shouldn't include that in the error message (it's still stored in the error if someone really needs that)