Fix: Unity Async Await Unobserved Task Exception

An async method throws. Your game continues running like nothing happened. The exception is swallowed because the Task wasn’t awaited. C# fire-and-forget tasks default to silent failure.

The Symptom

Async logic appears to run but produces no output. No error in console. State is half-updated. Sometimes a generic “A Task’s exception(s) were not observed” message appears minutes later from a GC finalizer.

What Causes This

An async Task method that throws stores the exception in the Task object. If nothing observes the Task (await, .Wait(), .Result, exception handlers), the exception is invisible until the Task is GC’d, at which point TaskScheduler.UnobservedTaskException fires — which Unity doesn’t log by default.

async void is worse: it has no Task at all, so the exception goes to the SynchronizationContext — which in Unity 2020+ surfaces as an unhandled exception, but only sometimes.

The Fix

Step 1: Log unobserved exceptions globally.

[RuntimeInitializeOnLoadMethod(RuntimeInitializeLoadType.BeforeSceneLoad)]
static void InstallTaskExceptionLogger()
{
    TaskScheduler.UnobservedTaskException += (sender, e) =>
    {
        Debug.LogError($"Unobserved task exception: {e.Exception}");
        e.SetObserved();
    };
}

Now any unobserved Task exception logs to Unity at GC time. Better than silent.

Step 2: Always await or fire-and-log.

// Bad
DoStuffAsync();   // fire and forget, silent on throw

// Good (caller is async)
await DoStuffAsync();

// Good (sync caller intentionally fire-and-forget)
_ = DoStuffAsync().ContinueWith(t =>
{
    if (t.IsFaulted) Debug.LogError(t.Exception);
});

Step 3: Use UniTask for Unity. Install com.cysharp.unitask. Replace Task with UniTask:

async UniTask LoadLevel(CancellationToken ct)
{
    var handle = Addressables.LoadAssetAsync<GameObject>("prefab");
    await handle.WithCancellation(ct);
    // continue
}

UniTask integrates with Unity’s PlayerLoop, doesn’t allocate, and gives you token-aware cancellation tied to GameObject lifetime via this.GetCancellationTokenOnDestroy().

async void Pitfalls

Reserve async void for Unity event handlers (UI button OnClick) where you can’t change the signature. Wrap the body in try/catch:

public async void OnButtonClick()
{
    try { await SaveGame(); }
    catch (Exception ex) { Debug.LogError(ex); }
}

Verifying

Throw deliberately in an async method. Without the global handler: silence. With it: error within a few frames. Switch to UniTask for cleaner cancellation and zero allocation.

Understanding the issue

AI bugs are emergent. The code is correct in isolation; the behavior emerges from interaction with other systems. Reproducing means controlling the interaction; fixing means deciding which interaction was wrong.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Await everything. Log unobserved. UniTask for serious code. Exceptions become visible.”

Related Issues

For coroutine stop, see StopCoroutine. For Burst managed allocation, see Burst BC1006.

Await. Observe. Cancel. Exceptions surface.