Quick answer: Key player data on a platform-independent master account ID, resolve the master at login, and on link merge the platform identity into the existing master rather than minting a new profile.
Cross-play account linking that produces duplicate profiles, splitting progression and cosmetics, comes from keying data on the platform ID instead of a unified account. A master-account model with explicit merge-on-link prevents the split.
How to fix it
1. Key data on a master account
Store progression, cosmetics, and currency against a platform-independent master account ID, with platform IDs as linked identities pointing to it.
2. Resolve master at login
On each platform login, look up the linked master account first and load that, rather than creating a new profile whenever an unfamiliar platform ID appears.
3. Merge on link, never duplicate
When linking a second platform, attach its identity to the existing master and merge any provisional data, instead of leaving two profiles that diverge.
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 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.