What causes an integration test asserting before an async scene load finishes?

The test triggers an asynchronous scene load and asserts immediately, but the scene's objects are not yet present because the load completes on a later frame.

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 an Integration Test That Asserts Before Scene Load Finishes

Quick answer: Await the load operation to completion by yielding until the AsyncOperation reports done, then assert on the loaded scene's contents.

SceneManager.LoadSceneAsync does not finish on the calling frame. Asserting before it completes finds nothing. Yielding until the operation is done fixes the race.

How to fix it

1. Yield until the load is done

In a [UnityTest] do var op = SceneManager.LoadSceneAsync(name); while (!op.isDone) yield return null; before asserting, so the scene is fully loaded first.

2. Confirm objects exist after load

Find required objects with GameObject.Find or a registry only after the operation completes; references captured before the load will be null or stale.

3. Unload in teardown

Call SceneManager.UnloadSceneAsync in teardown and yield until it finishes, so the loaded scene does not leak objects into the next test in the same play session.

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.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.