Quick answer: Preferences → External Tools → check the “Android NDK Installed with Unity (recommended)” box. Reinstall Android Build Support via Unity Hub if the path is empty. NDK version must match Unity’s expectation exactly — mismatched user NDKs cause every IL2CPP error in the book.

Build for Android. Spinner. “BuildPostprocessor.PostBuild error: NDK not found.” Or worse: minutes of compilation followed by a wall of IL2CPP linker errors. NDK mismatches are silently catastrophic.

The Symptom

Build fails with one of: “NDK directory does not exist,” “Failed to call 'arm-linux-androideabi-strip’,” or hundreds of undefined symbol errors during the libIl2CppCore link step.

What Causes This

Unity bundles a specific NDK version with each Unity LTS:

If External Tools points at a different version, or if the bundled NDK was never installed, builds fail. A common cause: developer pointed Unity at their own NDK from Android Studio (which is usually a newer version) thinking it would “just work.”

The Fix

Step 1: Use Unity-bundled NDK. Edit → Preferences → External Tools.

Android NDK Installed with Unity (recommended): ✓
Android JDK Installed with Unity (recommended):  ✓
Android SDK Tools Installed with Unity (recommended): ✓
Gradle Installed with Unity (recommended):       ✓

All four boxes ticked. Unity uses the versions it shipped, which match each other.

Step 2: Install if missing. If a box is greyed or paths are empty, the bundled tools were not installed. Open Unity Hub → Installs → gear icon next to your Unity version → Add Modules → check Android Build Support and its sub-modules: Android SDK & NDK Tools, OpenJDK. Install. Unity is now ready.

Step 3: Verify NDK version. Look at the External Tools NDK path. The path should contain a folder named like android-ndk-r23b. If yours is a major version off (r24 vs r23), Unity will fail at link time.

Native Plugin ABI Conflicts

If your project includes .so plugins (Firebase, AdMob, custom C++ code), each must be built for the ABIs you target (arm64-v8a, armeabi-v7a, x86_64). Mismatch shows as “dlopen failed: cannot locate symbol” on device or as a link failure.

Solution: Player Settings → Android → Other Settings → Target Architectures. Pick only architectures you have all plugins for. arm64 alone is fine for the Play Store.

Gradle vs Custom Build

If you ticked “Custom Main Manifest” or “Custom Gradle Properties” in Player Settings, the Gradle template files may reference NDK paths or versions. Check those template files for hardcoded paths and remove them or update.

Verifying

Build a fresh empty project for Android with all four bundled options ticked. If that fails too, the install is broken — reinstall via Unity Hub. If only your project fails, the issue is project-specific (custom Gradle, .so plugins, JNI sources).

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

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

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

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

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

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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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.

“Bundled NDK matches the Unity LTS. Don’t override unless you know why. ABI filters match plugins.”

Related Issues

For asmdef errors, see asmdef circular. For IL2CPP marshaling, see IL2CPP marshaling.

Bundled tools. Right ABIs. Builds succeed.