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 Sprite Atlas Including Duplicate or Missing Sprites

Q: What causes a Unity Sprite Atlas including duplicate or missing sprites?

A sprite is added to the atlas both individually and via its folder, or two atlases include the same folder, so a sprite gets packed twice or is split across atlases at runtime.

Quick answer: Add either the folder or the individual sprites to an atlas but not both, ensure each sprite belongs to exactly one atlas, and repack with Pack Preview to verify the contents.

Your build is larger than expected or a sprite renders from the wrong page, and the Sprite Atlas shows the same sprite twice. Overlapping inclusion rules cause duplicate or split packing.

How to fix it

1. Use one inclusion method

Add either the containing folder or the individual sprites to the atlas, not both. Including a folder and its members separately packs each sprite more than once.

2. Avoid overlapping atlases

Make sure two Sprite Atlases do not both include the same folder. A sprite should live in exactly one atlas, or it is duplicated and references can pick the wrong page.

3. Repack and verify

Click Pack Preview in the atlas inspector to see exactly what is packed, and check Include in Build is set as intended. Repack after fixing the inclusion rules.

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.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.