How to Debug Bugs That Only Happen on Real Devices

A bug that only happens on a phone will never show up in the editor. You have to debug it where it lives. Here is how.

How to fix it

1. Capture device logs

Pull platform logs and add remote error reporting so device-only failures arrive with stack traces and context.

2. Attach a remote debugger

Build a development build and attach the debugger or profiler to the running device to inspect state live.

3. Match the failing hardware

Reproduce on the same device class players report, since the bug is often specific to that GPU, OS, or memory tier.

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.