What causes the “Transform child out of bounds” exception in Unity?

Code indexes transform.GetChild(i) with an index that no longer exists — usually because children were destroyed or reparented while a loop was iterating over them.

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 “UnityException: Transform child out of bounds” in Unity

Quick answer: Never destroy or reparent children inside a forward loop over childCount; iterate backwards, snapshot the children first, or defer the structural change until after the loop.

This exception means you asked a Transform for child number i when it has fewer than i+1 children. It almost always appears when a loop mutates the hierarchy it is walking. Here is the fix.

How to fix it

1. Iterate backwards when destroying

Loop for (int i = transform.childCount - 1; i >= 0; i--) so removing child i does not shift the indices you have not visited yet.

2. Remember Destroy is deferred but reparenting is not

Destroy() removes the child at end of frame, but SetParent() and DestroyImmediate() change childCount instantly — mid-loop, that invalidates your bounds.

3. Snapshot children before mutating

Copy the children into a list first (foreach (Transform c in transform) list.Add(c);), then operate on the list — the snapshot stays stable while the hierarchy changes.

4. Guard dynamic indices

Anywhere an index comes from saved data or animation events, clamp it: if (i < transform.childCount) before GetChild(i).

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.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.