unity-ios-buildlisted
Install: claude install-skill tipoLi5890/unity-dev-skills
# unity-ios-build — from a Unity project to a process on the phone, without opening Xcode
An iOS build is **two builds and a delivery**, and each one fails in its own vocabulary:
> **Unity builds an Xcode project, not an app.** Exit 0 means a folder of generated C++ exists.
> Nothing has been compiled for the device, nothing has been signed.
>
> **`xcodebuild` builds the app.** This is where a native plugin first meets a compiler, and where
> signing is decided — by what this Mac holds, not by what `PlayerSettings` says.
>
> **`devicectl` delivers and launches it.** It is also the only log channel you have. There is no
> screenshot verb; what the app prints is what you know.
So "it built" is three separate claims. Make each one separately, and read each one back.
## Symptom → where to look
| The request | Go to |
|---|---|
| "build for iOS", "run it on my iPhone" | *The pipeline*, *Ready-made templates* |
| "No Account for Team", "No profiles for … were found", "is Xcode managed", "which team id" | `reference/signing-from-the-terminal.md` |
| "how do I read the iOS log", "it launches and nothing happens", "pull a file off the iPhone" | `reference/install-launch-console.md` |
| A native `.mm` plugin: "cannot use @try", "DllImport __Internal" | `reference/native-plugins.md` |
| Unity exits 0 and nothing was produced | `reference/headless-build.md` |
---
## The pipeline, and what proves each stage
| Stage | Command | Proof it happened |
|---|---|---|
| 1. Unity → Xcode p