Quick answer: Read logcat to find the actual error, package the architectures the device uses, and set a supported graphics API (try toggling Vulkan and OpenGL ES3.2) in the Android project settings.

An Unreal Android build that crashes at launch on device but runs in the editor needs logcat to diagnose. The usual causes are graphics API and packaging settings. Here is how to find yours.

How to fix it

1. Read logcat

Connect the device and capture logcat filtered for UE or your package name. The fatal error — a graphics init failure, a missing library, an assertion — is logged there and names the cause.

2. Package the right architectures

If the package omits the device's CPU architecture, it fails to load. Enable the architectures you target (arm64) in the Android settings and repackage.

3. Toggle the graphics API

Some devices fail on Vulkan or on OpenGL ES specifically. In the Android settings, try enabling only the supported API and disabling the other, then test which combination launches.

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

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.