What causes a UnityTest coroutine that never completes?

The test method yields on a condition that is never satisfied, or never yields back control, so the test runner waits forever and eventually reports a timeout.

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 UnityTest Coroutine That Never Finishes in Unity

Quick answer: Yield on a bounded wait with a timeout guard instead of an open-ended condition, and make sure every code path in the coroutine reaches a return.

A [UnityTest] returns IEnumerator and the runner drives it frame by frame. If you yield on a flag that never flips, the runner spins until it gives up. Add a timeout and assert on it.

How to fix it

1. Bound every wait

Replace while (!done) yield return null; with a loop that also tracks elapsed frames or seconds and breaks after a ceiling, then Assert.IsTrue(done). An unbounded wait turns a logic bug into a hang.

2. Yield real work, not nothing forever

Make sure the coroutine actually yield returns on each iteration so the runner regains control; a tight loop with no yield freezes the editor instead of advancing frames.

3. Check the condition can be reached

Verify the awaited callback or state change fires inside play mode at all. Edit-mode-only setup, disabled GameObjects, or an event subscribed after it fired will leave the flag permanently false.

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.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.