unity-device-testinglisted
Install: claude install-skill tipoLi5890/unity-dev-skills
# unity-device-testing — the phone is an instrument; prove it before you read it
A device run has three parties: the **app**, the **driver** (your script), and usually a **human**
who plugs, unplugs, waves or taps. Any of the three can be the thing that failed, and only one of
them is the thing you were testing.
> **"It didn't work on the phone."** Says nothing yet. The screen may have been off, the old build
> may still be installed, another app may hold the hardware, adb may have dropped, or the human did
> a different thing from the one you asked for. Every one of those produces the same symptom as a
> real bug.
So the rule is the one `unity-debug` applies to the editor, moved to hardware: **check the
instrument first**, and make the run say which of the three parties failed.
## Symptom → where to look
| The report | Go to |
|---|---|
| "test it on the phone", an acceptance run on real hardware | *The four parts*, then *Pre-flight* |
| "unplug / replug / background it and check" | `reference/human-in-the-loop.md`, `reference/android-driver.md` |
| "the screenshot is black", "adb lost the device" | *Pre-flight* |
| "how do I read logs from an iPhone" | *Two platforms, two log channels*, `reference/ios-driver.md` |
| "passes once, fails the next run", "compare two devices" | `reference/verdicts-and-evidence.md` |
| Stutters on device but runs fine in the editor | Confirm it on the device here (probe `diag` lines), then measure the frame-time window with `unity-profiling