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 a Unity Build Bloated by Development Build and Debug Symbols

Q: What causes a Unity build bloated by development build and debug symbols?

The build was made with Development Build enabled (or full debug symbols selected), so it ships profiling hooks, extra metadata, and larger symbol data than a release needs.

Q: How do you fix a Unity build bloated by development build and debug symbols?

Disable Development Build for releases and set debug symbols to the minimal level so the player build drops profiling support and unnecessary symbol bloat.

Quick answer: Disable Development Build for releases and set debug symbols to the minimal level so the player build drops profiling support and unnecessary symbol bloat.

Development builds include the profiler connection, script debugging, and extra metadata that no release needs, and full debug symbols add significant size. Turning these off for the shipping build reduces both size and overhead.

How to fix it

1. Turn off Development Build

In File > Build Settings, uncheck Development Build (and Script Debugging and Autoconnect Profiler) for release builds so profiling hooks are not compiled in.

2. Minimize debug symbols

Set the debug symbol level to the minimum your crash reporting needs; full symbols can balloon the build, while none or public-only is usually enough for release.

3. Automate the release config

Script your release build via build automation so it always uses the optimized settings, preventing a stray development build from shipping.

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.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.