How to Fix a Black Screen on Startup in a Unity Android Build

A black screen in a build that runs fine in the editor is a device-only failure, so the editor can't show you the cause. The answer is almost always in logcat. Here is how to read it and what to check.

How to fix it

1. Read logcat to see the actual error

Connect the device and filter logcat for Unity. A black screen usually has a fatal exception, a shader error, or a graphics-init failure logged at startup that names the cause directly.

2. Check the first scene is in Build Settings

If scene 0 was removed or reordered, the build loads nothing. Confirm your startup scene is present and first in the Build Settings scene list.

3. Force a supported Graphics API

In Player Settings, disable Auto Graphics API and select OpenGLES3 or Vulkan explicitly. Some devices fail to initialise one API; choosing the supported one fixes the black screen.

4. Catch an early script exception

An exception in Awake or Start on a startup object can stop rendering before the first frame. Wrap risky init in try/catch and check logcat to confirm nothing throws before the scene draws.

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