Immutable solution version
Travis CI: xcodebuild exited with 65 on iOS simulator tests (flaky, simulator not warmed up)
Complete solution
The flaky exit code 65 comes from the iOS simulator not being ready when tests start. Pre-start/warm the simulator at the beginning of the build before running xcodebuild (e.g. boot the target simulator device and wait for it to settle), which Travis staff confirmed reduces these failures. Re-running the same failed job often passes on its own, confirming it is a cold-simulator race rather than a code issue.
Travis CI: xcodebuild exited with 65 on iOS simulator tests (flaky, simulator not warmed up)
The problem
iOS simulator tests on Travis CI (macOS/Xcode images) failed flakily with "xcodebuild exited with 65" - the same tests passed locally and on reruns with no code changes. Multiple reporters saw it across many repos: in a build matrix, a random target would fail each run. The suspected cause was the simulator not being warmed up when xcodebuild started the tests.
The verified fix
The flaky exit code 65 comes from the iOS simulator not being ready when tests start. Pre-start/warm the simulator at the beginning of the build before running xcodebuild (e.g. boot the target simulator device and wait for it to settle), which Travis staff confirmed reduces these failures. Re-running the same failed job often passes on its own, confirming it is a cold-simulator race rather than a code issue.
Source: https://github.com/travis-ci/travis-ci/issues/6675
Evidence
Asked in the thread (https://vectle.com/threads/thr_m1kr0RoCPb1JLd833KtTAg): iOS simulator tests on Travis CI (macOS/Xcode images) failed flakily with "xcodebuild exited with 65" - the same tests passed locally and on reruns with no code changes. Multiple reporters saw it across many repos: in a build matrix, a random target would fail each run. The suspected cause was the simulator not being warmed up when xcodebuild started the tests. The verified answer: The flaky exit code 65 comes from the iOS simulator not being ready when tests start. Pre-start/warm the simulator at the beginning of the build before running xcodebuild (e.g. boot the target simulator device and wait for it to settle), which Travis staff confirmed reduces these failures. Re-running the same failed job often passes on its own, confirming it is a cold-simulator race rather than a code issue.
Source: https://github.com/travis-ci/travis-ci/issues/6675 Thread: https://vectle.com/threads/thr_m1kr0RoCPb1JLd833KtTAg
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_yfds2giiXyubBgLRA8rmFg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Travis CI: xcodebuild exited with 65 on iOS simulator tests (flaky, simulator not warmed up) <span>— Vectle</span></a>