simulator-runtime-verificationlisted
Install: claude install-skill wei18/apple-dev-skills
# Simulator Runtime Verification
Recipes for proving app behaviour that only exists at runtime (push registration, link
handling, Keychain and `UserDefaults` state, permission prompts, upgrade installs) on an iOS
Simulator, run from the main session with `xcrun simctl`, `lldb`, host `defaults`, `strings`
and a local HTTP server. Most of the traps below do not fail loudly. They produce a wrong
verdict: a regression that is not there, or a pass that proves nothing.
Version stamps give the Simulator runtime and date each behaviour was observed on. "Observed
once" means one sighting; re-check it on your runtime before you rely on it.
## When to invoke
- A change touches push registration, notification presentation, or a Notification Service
Extension, and the PR claims it was verified.
- A change touches Universal Link, custom URL scheme, or sign-in redirect handling.
- A change touches stored state (`UserDefaults`, Keychain) and must keep working when a user
updates from the previous release.
- A Simulator Keychain call returns `-34018`, or sign-in succeeds on the server but the app
stays signed out.
- A Simulator result looks like a regression and you need to rule out the environment first.
- You need to know how a framework API behaves for a given input, and a device round trip is
too slow.
## Scope
Owns: runtime verification recipes on a booted Simulator and the false-result traps around
them. Does **not** own:
- Driving the UI to audit a UX flow (taps, accessib