docs: record confirmed CoreSimulator runner blocker
Android validation / emulator (35) (push) Failing after 4s
Android validation / emulator (37.0) (push) Failing after 9s
iOS validation / simulator (push) Failing after 1m5s
Android validation / build (push) Successful in 5m16s

Follow-up Mac job 1066 passed Node/checkout/Xcode/Swift lookup, then correctly failed the bounded simctl device-list probe after sixty seconds. Record the exact administrator-owned blocker without claiming Apple app validation.
This commit is contained in:
Yuvomi Mobile Contributors committed 2026-10-21 09:38:59 +02:00
1 parent 92dbd0e06d
commit 129eac675c
4 files changed
+18 -6

No files matched your search

+3 -1
View File
@@ -50,7 +50,9 @@ native bootstrap and checkout were verified in Mac job 1062 (run 661/#6).
That job subsequently stalled in Apple-tool preflight after printing Xcode 27.1.
The preflight now prints each tool probe and bounds it to 60 seconds using Python
(`scripts/check-apple-tools.py`), so the next run identifies the unresponsive
command rather than hanging silently. This does not validate the iOS app.
command rather than hanging silently. Follow-up job 1066 (run 663/#8) verified the
diagnostic: Xcode and Swift lookup pass, but `xcrun simctl list devices available`
times out. This is a runner prerequisite failure, not an iOS application test.
If an Apple probe stalls, run the named command in the runner user's interactive
login session, check the selected full Xcode, finish its first-launch components