Exporting to Android

Export requires Android templates matching your engine build, a Java SDK and an Android SDK. Running a Windows project does not establish Android component availability, particularly for C# and native plugins.

Prepare

1. Create an Android export preset. Set editor paths export/android/java_sdk_path and export/android/android_sdk_path to the Java and Android SDK roots.
2. Match tools to the current template. Source configuration specifies Java 17, compile/target SDK 36, build-tools 36.1.0 and minimum SDK 24. These are template values, not a promise of future store-policy compliance.
3. Install matching export templates. C# requires a .NET-enabled variant; a third-party native library needs an ABI for each selected device architecture.
4. Set a unique package identifier, version and architectures. Enable permissions according to actual requirements.
5. Export a debug APK first and install it on a device. Check input, audio, pause/resume, saves and resource loading.

Release

Configure your own release keystore and alias. Back up the key separately; keep passwords out of published files. Use Gradle for AAB and Android-project modifications. A debug APK does not validate release signing or an AAB’s readiness for publication.

Diagnose export failures

Missing template: match build and variant. Missing Java/SDK: verify root directories and tools within them. Installation error: compare package identifier and the previously installed app’s signing identity. Crash after installation: retain logs and symbols.

This procedure was source-reviewed; export, device installation and store release were not executed here.