Publishing

Build for Android

Android SDK, NDK, JDK, icon, signing.

Build for Android

Android publishing uses an installed Qt Android development kit with a compatible SDK, NDK, and JDK.

Toolchain Settings

Choose Recommended (Auto Detect) or Custom Paths. Recommended means using compatible detected installations; the SDK, NDK, and JDK are not bundled inside the website or editor ZIP.

Build Settings

  • Select the Android platform.
  • Set a unique Android Package ID.
  • Choose APK/AAB where supported.
  • Enter the game Product Name and Version.
  • Select a square high-resolution PNG icon and optional startup logo.
  • Choose an output directory.

CMake Paths on Windows

When passing resource paths to CMake, use normalized forward slashes. For example:


C:/Users/User/AppData/Local/Temp/AmzaAndroidBuild/package/res/mipmap-hdpi/amza_game_icon.png

A path containing raw C:\Users can cause a CMake Invalid character escape '\U' error in certain generated files. Update to a release containing the path normalization fix.

Signing

A release APK/AAB needs appropriate signing configuration. Debug signing is not a substitute for a production release key.

Validation

Check the full CMake error before reinstalling the toolchain. Confirm the resulting package installs and renders correctly on a real device.