Fix: Unity AR Foundation Tracking Lost After App Pause

Here is how to fix Unity AR Foundation apps that lose all placed AR content after the player tabs away and back. Your virtual furniture, characters, or markers reposition randomly or vanish. The cause is the underlying ARKit (iOS) or ARCore (Android) session being suspended and a new session starting on resume, often with a different world origin.

The Symptom

User places content in the AR scene. They lock the phone or switch apps. On return, content is in the wrong location, floating in space, or gone entirely. Console may show Tracking lost or Session reinitialized messages.

What Causes This

Session teardown on backgrounding. Mobile OS suspends camera and sensor access. AR Foundation pauses the session. On resume the session restarts and the world coordinate origin may differ.

No anchors on placed content. Without ARAnchor components, placed objects exist in arbitrary world coordinates. Without an anchor, the system has no way to relocalize them.

Failed relocalization. If the camera does not see enough of the original environment to relocalize, tracking returns but anchors are not restored.

Reset called too aggressively. Some templates call ARSession.Reset on every resume, wiping anchors and starting fresh.

The Fix

Step 1: Anchor every placed object.

using UnityEngine;
using UnityEngine.XR.ARFoundation;

public class PlaceContent : MonoBehaviour
{
    [SerializeField] private ARAnchorManager anchors;
    [SerializeField] private GameObject prefab;

    public void PlaceAt(Pose pose)
    {
        ARAnchor anchor = anchors.AddAnchor(pose);
        var spawn = Instantiate(prefab, pose.position, pose.rotation, anchor.transform);
        // Spawn now follows anchor through pause/resume
    }
}

Anchors are tracked by the AR system across sessions when relocalization succeeds.

Step 2: Watch session state.

void OnEnable()
{
    ARSession.stateChanged += OnSessionState;
}

void OnDisable()
{
    ARSession.stateChanged -= OnSessionState;
}

void OnSessionState(ARSessionStateChangedEventArgs args)
{
    switch (args.state)
    {
        case ARSessionState.SessionInitializing:
            ShowHint("Move your phone slowly");
            break;
        case ARSessionState.SessionTracking:
            HideHint();
            break;
        case ARSessionState.NotTracking:
            ShowHint("Tracking lost. Point at a textured surface.");
            break;
    }
}

Step 3: Handle pause and resume explicitly.

void OnApplicationPause(bool paused)
{
    if (paused)
    {
        // AR session pauses automatically. Save anchor data if needed.
        SaveAnchors();
    }
    else
    {
        // Wait for relocalization before judging tracking quality
        StartCoroutine(WaitForTracking());
    }
}

IEnumerator WaitForTracking()
{
    float deadline = Time.time + 5f;
    while (Time.time < deadline && ARSession.state != ARSessionState.SessionTracking)
        yield return null;

    if (ARSession.state != ARSessionState.SessionTracking)
        ShowResetButton();   // only if user truly cannot recover
}

Step 4: Use AR World Map (iOS) for persistence. ARKit supports saving the entire world map to disk. Restore on next launch to retain all anchors and surface understanding. Android has Cloud Anchors for similar purposes.

Step 5: Avoid ARSession.Reset on resume. Reset is a nuclear option that destroys all anchors. Use it only when the user explicitly chooses to start over. For normal pause/resume, let AR Foundation handle session lifecycle.

UX For Tracking Loss

Show a clear, friendly hint when tracking degrades: “Look around the room slowly to recover.” Pause gameplay or fade content while NotTracking. Resume gracefully when state returns to SessionTracking. Players forgive a few seconds of recovery; they do not forgive content vanishing without explanation.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

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

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

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.

“Anchors survive sessions when relocalization succeeds. Without anchors, every pause is a fresh start with new coordinates.”

Related Issues

For pause-related lifecycle issues, see Unity Crashes on Exit. For mobile audio after pause, see Audio Silent After Tab Switch.

Anchor everything. Subscribe to stateChanged. Reset only as last resort. Tracking returns gracefully.