What causes install and trust errors when deploying iOS test builds?

The device refuses the build's signature — free/dev certificates needing manual trust, the device missing from the provisioning profile, expired profiles/certs, or unsupported iOS versions for the build.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix “Unable to Install” and “Untrusted Developer” Errors When Testing iOS Games on Device

Quick answer: Trust the developer profile on the device, ensure the device UDID is in the profile, refresh expired signing, and match deployment target to the device's iOS.

Deploying to hardware trips over Apple's trust chain in predictable places. The remedy ladder is short. Here it is.

How to fix it

1. Trust the profile on device

Settings > General > VPN & Device Management > your developer entry > Trust — required for dev-signed installs outside TestFlight; free accounts re-require it weekly.

2. Register the device

Ad-hoc/development profiles are UDID-allowlists — add the device in the developer portal (or let Xcode's automatic signing do it) and rebuild with the refreshed profile.

3. Refresh expired signing

Certificates and profiles expire; Xcode's Signing & Capabilities pane shows the state — renew, and remember free-account builds expire on device after 7 days.

4. Prefer TestFlight for testers

External testers should never touch UDIDs and trust dialogs — TestFlight removes the whole class; save direct installs for your own iteration.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every mobile error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.