Fix: Godot 4 Export Template Missing for Android Debug

Godot stops the export with “export template not found” or builds for ten seconds and then fails with a Gradle error pointing at a missing template directory. Three different settings can produce the same error.

The Symptom

Project → Export → Android → Export Project. Either the dialog refuses to start with “Template missing,” or it runs Gradle and fails partway through with a path-not-found error referencing the templates folder.

The Three Causes

Cause 1: Templates not installed for this exact version. Editor 4.3.2 needs 4.3.2 templates. A 4.3.1 set won’t work. Templates download as a single archive of the matching binary blobs.

Cause 2: Custom path mismatch. Editor Settings → Export → Android lists paths to ADB, JDK, and the Android SDK. If any are blank or wrong, even a working template fails to package.

Cause 3: Gradle build template not installed in project. If your export preset has Use Gradle Build = true (recommended for plugins, custom Android extensions, or AAB output), the editor expects an android/build/ folder inside the project. Without it, exports fail.

The Fix

Step 1: Install editor templates. Editor menu → Manage Export Templates. The dialog shows installed and missing versions. Click Download & Install for your editor version. Wait; the archive is ~600 MB.

Step 2: Install the Android Build Template into the project (Gradle path only). Project menu → Install Android Build Template. This unpacks into res://android/build/. You only do this once per project; commit the folder.

Step 3: Configure paths. Editor Settings → Export → Android:

Android SDK Path:    /Users/you/Library/Android/sdk
Java SDK Path:       /Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home
Debug Keystore:      /Users/you/.android/debug.keystore
Debug Keystore User: androiddebugkey
Debug Keystore Pass: android

Step 4: Generate a debug keystore (if missing).

keytool -genkey -v -keystore debug.keystore \
        -storepass android -alias androiddebugkey \
        -keypass android -dname "CN=Android Debug,O=Android,C=US" \
        -keyalg RSA -validity 10000

Move the resulting file somewhere stable (~/.android is conventional) and point the editor setting at the absolute path.

One-Click Verification

Project → Export. Pick your Android preset. Click the “Manage Export Templates” gear if anything is red. The dialog tells you in plain English which file or path is missing.

Custom Modules & Plugins

If you build Godot from source with extra modules, you also have to build matching Android templates with the same modules. The official template archive only includes stock modules. scons platform=android target=template_debug arch=arm64 from the source tree produces the matching APK template.

AAB Output for Play Store

The Play Store requires AAB, not APK. With Gradle Build template installed, your preset has an AAB option in the export dropdown. Without it, only APK is available. AAB also requires a release keystore separate from the debug one.

Understanding the issue

Export pipelines transform development assets into shipping packages. Each transformation can introduce subtle changes that produce bugs only visible in the exported build.

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 Godot. 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

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

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 Godot-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 Godot, 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

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.

“Editor templates for the right version. Build template into the project for Gradle. Keystore on absolute path. Builds.”

Related Issues

For iOS export issues, see Godot iOS export. For desktop export missing libs, see Windows template.

Templates. Build template. Keystore. Build runs.