How to Fix a Quality Preset That Resets Every Launch Despite Being Saved

A mobile player sets quality to High but it is Low again next launch, because the app was killed in the background and the on-quit save never ran. Save on change and flush.

How to fix it

1. Save on change, not on quit

Write the setting the moment it changes (or on a debounced timer) rather than waiting for an exit handler that may never fire on mobile.

2. Flush the write

Ensure the persistence layer actually flushes to storage (PlayerPrefs.Save() or an explicit file flush) so the data is durable before the app can be killed.

3. Handle pause/background

Also save in the pause/background lifecycle callback, which is the most reliable hook before the OS reclaims the process.

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