Why are AssetBundle materials pink on mobile but fine in editor?

The shader variant required by the AssetBundle was stripped from the player build because no scene used it. Add the shader to Always Included Shaders, ship a ShaderVariantCollection that captures the needed variants, and warm it up at startup.

How do I capture all shader variants used by an AssetBundle?

Enable Save to Asset under Project Settings > Graphics > Shader Loading > Log Shader Compilation. Run through your scenes and AssetBundles in the editor with the relevant assets visible. Save the resulting ShaderVariantCollection and add it to your build.

Why do my variants survive in editor but get stripped at build?

Build-time shader stripping prunes variants based on what scenes reference. AssetBundles built separately do not participate in that scan. Either build AssetBundles with the same player so variants are kept, or include a SVC asset and warm it.

Fix: Unity AssetBundle Shader Pink on Mobile

Quick answer: The shader variant the AssetBundle needs was stripped because no scene in the player referenced it. Add the shader to Always Included Shaders and ship a ShaderVariantCollection capturing the variants. Warm it at app startup.

Here is how to fix Unity AssetBundles whose materials render solid pink (Unity’s missing-shader fallback) on mobile while looking fine in the editor. The shader exists in the bundle. The material reference is correct. But the variant the material needs was stripped from the player build because no scene at build time used that exact combination of keywords. Mobile builds are aggressive about stripping; AssetBundles bear the brunt.

The Symptom

You ship a base APK / IPA and download AssetBundles for content. In editor, everything renders correctly. On device, AssetBundle assets render solid pink/magenta. Console may log Could not find compatible shader variant.

What Causes This

Variant stripping. The build pipeline scans scenes and includes only variants used. If a material in an AssetBundle uses a unique keyword combination not seen in any scene, that variant is stripped from the player.

Shader not in Always Included. Shaders only used at runtime via AssetBundles can be stripped entirely if no scene references them.

Different graphics tier. Some shaders compile differently per tier (Mobile, Low, Medium, High). Editor uses high tier; mobile uses Tier 1. Variants for Tier 1 may not exist in your build.

Keyword collisions. Materials in AssetBundles may set custom keywords your in-scene materials never set. Those keyword permutations are not captured by build-time scanning.

The Fix

Step 1: Add shaders to Always Included Shaders. Open Project Settings → Graphics → Always Included Shaders. Click + and add every shader your AssetBundles reference. This guarantees the shader binary ships, even if no scene uses it.

Step 2: Build a ShaderVariantCollection. Open Project Settings → Graphics → Shader Loading. Enable Log Shader Compilation and Save to Asset. Run through every scene and AssetBundle preview in the editor. Unity records every variant used. Export as ShaderVariantCollection (.shadervariants).

Step 3: Ship and warm the SVC.

using UnityEngine;

public class VariantWarmer : MonoBehaviour
{
    [SerializeField] private ShaderVariantCollection variants;

    void Awake()
    {
        if (variants != null && !variants.isWarmedUp)
        {
            variants.WarmUp();
            DontDestroyOnLoad(gameObject);
        }
    }
}

Drop this on a bootstrap object. WarmUp may take a few hundred milliseconds; show a loading splash if needed.

Step 4: Build AssetBundles for the same target as the player.

// Editor build script
BuildPipeline.BuildAssetBundles(
    outputPath,
    BuildAssetBundleOptions.None,
    BuildTarget.Android);   // match player platform

An AssetBundle built for one platform with one graphics API may not work on another. Always build per platform.

Step 5: Disable Strict Variant Stripping during diagnosis. In Project Settings → Graphics → Shader Loading → Strip From Build, set to None temporarily. Build. If the AssetBundle now renders correctly, stripping was the cause — turn back on with the SVC in place.

URP/HDRP Shader Stripping Settings

SRPs have additional stripping in their respective asset settings. Open the URP Asset and check options like Strip Unused Variants. Disable per-quality-level toggles if you ship a single quality. For HDRP, Project Settings → HDRP Asset → Shader Stripping.

Verifying On Device

Run with UNITY_LOG_SHADER_COMPILATION:

# Build with Development Build + Script Debugging on
# Run on device, capture logcat (Android) or Console.app (iOS)
# Look for "Compiling shader variant" or "Failed to find compatible shader variant"

The latter pinpoints exactly which variant is missing.

Understanding the issue

Shader bugs manifest visually but trace to invisible state. Triage requires understanding the runtime context as much as the source.

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

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

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

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

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

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

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.

“Always Included Shaders + ShaderVariantCollection + warm at startup. The triple that keeps AssetBundle pink at bay.”

Related Issues

For URP-specific shader build issues, see URP Shader Not Rendering. For variant collection issues, see Variant Collection Missing.

Always Include the shaders. Capture the variants. Warm at startup. The pink goes away.