"Failed to get launch progress" error when running test through build pipeline
- Dominant language
- Objective-C
- Stars
- 5.7k
- Forks
- 737
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 5
Description
Hi, last week my team was integrating EarlGrey 2.0 into our project using Xcode 11.1, and managed to get tests passing when run locally. However, when we run the tests through fastlane as a part of our automated build pipeline, we sometimes get failures with the message:
```xxx_sample_ios_EarlGreyUITests.LaunchTest
testLaunchPerformance, Failed to get launch progress for :
Expired token: no operation still exists for this token.
XCUIApplication+GREYTest.m:86
Executed 1 test, with 1 failure (0 unexpected) in 6.075 (6.077) seconds
```
As far as I could tell, this error only happened when running a test that included some use of EarlGrey. I tried having a loop to keep trying `let app = XCUIApplication().launch()` until the app exists, but that did not fix the problem. Any recommendations on how to solve this problem?
Contributor guide
Research direction
Start by examining the EarlGrey failure location named in XCUIApplication+GREYTest.m:86 and compare local test runs with the fastlane build pipeline described in the report. Reproduce the intermittent launch-progress failure under Xcode 11.1, then determine the pipeline-specific cause and verify that the affected EarlGrey test completes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- objective-c
- Domain
- mobile-dev, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100