Quick answer: Before syncing down, compare an in-save monotonic counter or total playtime between cloud and local, and keep the newer one (prompting the player on a true conflict).

Play offline, then reconnect, and a naive sync pulls the old cloud save over your newer local one. Compare an in-file version before overwriting and the loss stops.

How to fix it

1. Track a monotonic save counter

Increment a counter in the save on every write, both offline and online. This, not timestamps, is your source of truth for which copy is newer.

2. Compare before pulling down

On reconnect, fetch the cloud counter, compare it to local, and only overwrite local if cloud is strictly newer. Otherwise push local up instead.

3. Prompt on genuine conflicts

If both sides advanced independently (same base, divergent edits), show the player both saves with playtime/timestamp and let them choose rather than silently picking one.

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.

A crash you can name from its stack trace is a crash you can usually fix in minutes.