ios-simulator-boot-health
Skill6 starsChanged 34 days agoMITView on GitHub
Diagnose and handle iOS simulator boot failures on the shared Mac when running scripts/test-ios.sh - "PosterBoard status -5", exit 77 (no healthy simulator), settle-gate REJECT, a shard that ran no tests. Use before re-running, erasing or shutting down any simulator, and when judging whether a test run actually passed.
In this repository79 other files it gives its agents.
- adr-phase-coverageSkill
- aposd-red-flag-reviewSkill
- apple-on-device-aiSkill
- artifact-gatesSkill
- asc-app-create-uiSkill
- asc-build-lifecycleSkill
- asc-cli-usageSkill
- asc-crash-triageSkill
- asc-id-resolverSkill
- asc-localize-metadataSkill
- asc-metadata-syncSkill
- asc-notarizationSkill
- asc-ppp-pricingSkill
- asc-release-flowSkill
- asc-revenuecat-catalog-syncSkill
- asc-shots-pipelineSkill
- asc-signing-setupSkill
- asc-submission-healthSkill
- asc-subscription-localizationSkill
- asc-testflight-orchestrationSkill
- asc-wall-submitSkill
- asc-workflowSkill
- asc-xcode-buildSkill
- choose-boring-technologySkill
- ci-preflightSkill
- conways-lawSkill
- cost-routingSkill
- cost-tier-routingSkill
- cunninghams-lawSkill
- ddd-strategic-auditSkill
- ddd-tactical-reviewSkill
- debug-test-captureSkill
- developing-ios-appsSkill
- doerrs-lawSkill
- fitts-lawSkill
- fix-regression-guardSkill
- galls-lawSkill
- goodharts-lawSkill
- greenspuns-tenth-ruleSkill
- gsd-core-hooksSkill
- hofstadters-lawSkill
- hyrums-lawSkill
- ios-accessibilitySkill
- kerckhoffs-principleSkill
- kernighans-lawSkill
- knuths-optimization-principleSkill
- lady-lovelaces-objectionSkill
- leaky-abstractionsSkill
- linuss-lawSkill
- mobile-ios-designSkill
- money-boundary-judgmentSkill
- moores-lawSkill
- no-deferSkill
- norvigs-lawSkill
- parkinsons-lawSkill
- peter-principleSkill
- postels-lawSkill
- post-fix-traceSkill
- qa-test-architectSkill
- rubber-duckSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 32
Never: simctl erase all, killall Simulator, killall com.apple.CoreSimulator.CoreSimulatorService (kills other sessions' booted sims).
- Very specific: line 37
Not done: golden simctl clone (rec.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
iOS simulator boot health (shared Mac)
This Mac is shared with other sessions. Only two simulators are ours: iPhone 17 (85330DFD-25C3-402F-A529-36CA09154BC1) and iPhone 18 Pro Max (5CEF7C7B-7E33-40F7-B5D8-4736CD14222F). iPhone 18 Pro and iPhone 17e belong to another session; iPhone Air is avoided. Rotate between ours per run (memory rotate-ios-simulators).
What the failure is
PosterBoard status -5 in <results>-diag/settle.txt is the wrapper reading launchctl list column 2 for com.apple.PosterBoard inside the simulator (scripts/lib/ios-diag.sh, coincert_diag_settle_sample). Negative status = killed by that signal; -5 = SIGTRAP. It is a real crash, not an over-strict check: macOS wrote PosterBoard-*.ips for it (6 reports 10-25..10-26, 5 in +[NSURL(PosterFoundation) pf_posterPathInstanceURLForVersionsURL:version:], an assert while ingesting a poster version at first boot). No jetsam, memory or disk signal. Cause is unconfirmed (stale poster store is likely, unverified). Full evidence: references/posterboard-research.md.
Run it this way
COINCERT_SIM_PINNED_ERASE=1 COINCERT_SIM_UDID=<ours> COINCERT_SIM_NAME=<name> \
COINCERT_DERIVED_DATA=/private/tmp/claude-501/derived-X scripts/test-ios.sh ...- One
test-ios.shat a time; never edit source while one builds. - With
COINCERT_SIM_PINNED_ERASE=1a pinned device gets two boot attempts (coincert_sim_try_budget): reject -> scopedsimctl erase <that UDID>-> one retry. Without it a pinned device gets one attempt and is not erased. - On a rejection the diag folder now holds the matching
PosterBoard-*.ipsandposter-watchlines insettle.txt(PosterBoard pid/status for ~20 s after the reject;COINCERT_SIM_POSTER_WATCH=0to skip). These observe only; the device is still rejected.
Judge a run only by its log and xcresult
Never by a background task's exit status (a command ending in echo exits 0 after a failed boot). A run passed only if: the Test run with N tests ... passed line is present, there is one TEST EXECUTE SUCCEEDED, no relaunch lines, console count = xcresult total, and every skip is explained. Four whole-shard attempts once ran no tests and looked fine from the exit status.
Safe / unsafe
Safe: simctl shutdown|erase <one UDID> on a device this run booted; reading ~/Library/Logs/DiagnosticReports; simctl diagnose --udid.
Never: simctl erase all, killall Simulator, killall com.apple.CoreSimulator.CoreSimulatorService (kills other sessions' booted sims); touching a simulator this run did not boot. Clean up (shut down, erase if it will not boot) only the devices our run used.
Open items
- Whether PosterBoard recovers after the SIGTRAP is unverified; the reject was deliberately not softened. Read the
poster-watchlines of the next real failure before changing the gate (research rec. 2). - Not done: golden
simctl clone(rec. 5, unverified benefit), boot lock (rec. 4, low benefit).bootstatus -bis already used. - Apple Feedback is still to be filed with the
.ips(symbolpf_posterPathInstanceURLForVersionsURL). - Pinned + recently-erased device takes the recreate path in
ios-repair.sh, which deletes the pinned device and invalidates the pin.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

