How to Run a Smoke Test on a Real Device From CI

A build that boots on a server but crashes on a phone still ships if you do not test on devices. A device smoke test catches it. Here is how.

How to fix it

1. Deploy to a device

Install the build on a real or cloud-hosted device from CI.

2. Boot into gameplay

Run a smoke test that reaches a gameplay scene and verifies core systems started.

3. Fail on device crashes

Treat a device-side crash as a pipeline failure so it never reaches players.

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 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.