Fix Unity ScriptableObject Singleton Null After Build

This bug always shows up at the worst time: the build looked fine until you launched it and saw a cascade of NullReferenceException errors on your game’s config object. The ScriptableObject is there in your project, it works in Play mode, and it still returns null the moment you hit F5 on the standalone player. The problem is how the asset gets into the build, not how it loads.

Understand what Unity ships

When Unity packages a build it walks the dependency graph starting from scenes listed in Build Settings. Any prefab, material, texture, or ScriptableObject reachable through that graph is included. Anything else is stripped. This is intentional — it keeps your build small — but it catches out anyone who loads assets by path only.

There are four ways to make a ScriptableObject asset survive the strip:

• Reference it directly from a field on a MonoBehaviour in a built scene.
• Place it inside any folder named Resources and load with Resources.Load.
• Mark it Addressable and load via the Addressables API.
• Pack it into a classic AssetBundle and load that bundle at runtime.

The direct reference pattern

The cleanest approach for a singleton is a bootstrap MonoBehaviour in your first scene that holds a serialized reference to the asset and publishes it through a static field:

public class GameConfigBootstrap : MonoBehaviour {
    [SerializeField] private GameConfig config;

    void Awake() {
        GameConfig.Instance = config;
        DontDestroyOnLoad(this.gameObject);
    }
}

Because the field is serialized and the GameObject lives in a built scene, Unity includes the asset automatically. You do not need Resources and you cannot forget to register it.

When Resources is acceptable

For small, always-loaded config that you genuinely want available before any scene loads, Resources is fine. Move the asset into a folder literally named Resources anywhere in Assets/, drop the extension from the load call, and be aware that every file under those folders ships regardless of references:

public static GameConfig Instance => _instance ??= Resources.Load<GameConfig>("GameConfig");

If Resources.Load returns null in a build, the most common causes are a misspelled path, the file not actually being in a Resources folder, or an extension accidentally included in the string.

Addressables gotchas

Addressables solve the same problem with async loading and remote content, but they introduce their own failure modes. An entry must be present in the Addressables settings at build time; the content catalog must be built alongside the player. If you enable “Use Asset Database” for local runs and forget to swap to “Use Existing Build” before the player build, the catalog will be missing. Always build content with “Build -> New Build -> Default Build Script” before the player build on CI.

Never rely on AssetDatabase at runtime

AssetDatabase and anything under UnityEditor is stripped from builds. If your singleton’s lazy getter calls AssetDatabase.LoadAssetAtPath, it will compile only because the call is inside an #if UNITY_EDITOR block or behind a platform check — and the block returns null on the player path. Search your codebase:

# Quick audit
grep -rn "AssetDatabase.Load" Assets/Scripts/

Every hit needs a runtime equivalent, not a silent fallback.

Understanding the issue

Build pipelines transform development assets into shipping packages. Each transformation can introduce subtle changes: compression, stripping, format conversion, code generation. A bug that only appears in the cooked build is usually one of these transformations doing something the author didn't expect.

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

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

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

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

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

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

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.

“If the asset does not appear in the Build Report, it is not in the build. Stop debugging your loader and start debugging your references.”

Related Issues

For similar editor-versus-build discrepancies, see Fix Unity prefab variant overrides being lost. For singleton lifecycle in another engine, Fix Godot autoload singleton not accessible covers the same failure mode.

Tip: open the Build Report window after every build — if your singleton is missing there, you already know where to look.