What causes a flaky Unity test that depends on WaitForSeconds timing?

The test waits a fixed number of seconds and then asserts, but the work it waits for finishes at a variable time depending on frame rate and CI load, so the assertion sometimes runs too early.

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 Flaky Unity Test That Depends on WaitForSeconds Timing

Quick answer: Wait for the actual condition with a polled timeout instead of a fixed sleep, and drive time deterministically where possible.

yield return new WaitForSeconds(1f) assumes the work is done after one second. On a loaded CI agent it is not, and the assert fires against stale state. Poll for the result instead.

How to fix it

1. Wait on the result, not the clock

Replace the fixed wait with a loop that yields each frame until the expected state is reached, with a generous timeout that fails the test if it never happens. This removes the race.

2. Use WaitForSecondsRealtime carefully

If you must wait, prefer WaitUntil(() => condition) so the test proceeds the instant the work completes rather than after an arbitrary delay.

3. Make timing deterministic

Where the system under test reads delta time, inject a fixed step so the test does not depend on the agent's real frame rate at all.

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 errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.