Studio v0.2.0
Studio v0.2.0 · Product manual

Build an Android project, APK or AAB

Build an Android project, APK or AAB — GalCraft Studio product manual.

Choose Android in Publishing, then select the installed Android 0.1.1 target builder. Install the target package in Plugins if the catalog is empty. Follow the overview to apply release settings, save the work and check target assets.

1. Configure the app

FieldValue
Application ID (applicationId)For example com.example.springlights; at least two segments, each starting with a lowercase letter and using lowercase letters, digits or underscores
Build number (versionCode)Integer 1–2100000000; start at 1 and increment for subsequent releases
OrientationLandscape or Both landscape orientations; default Landscape
OutputComplete Android project, APK or AAB

The current template fixes minSdk 26 and targetSdk 35. Target capabilities and versions lists the builder, architectures and tools. The Android icon uses the saved work image and accepts PNG, JPEG or WebP.

2. Export the complete project

Choose Complete Android project, select a dedicated output, choose Check and build. Its android-project/ contains the Gradle project, Player, snapshot, resources and native bridge. Open the entire project in Android Studio to configure its JDK, SDK and signing.

Project export prepares files directly. Tool detection/download belongs to the APK/AAB path. Configure signing in Android Studio through Build → Generate Signed Bundle/APK, choosing an output and your keystore and alias. Follow the official Android signing guide.

3. Prepare APK/AAB tools

  1. Choose APK or AAB. Enter Tool download location or use Choose tools directory. The default is .galcraft/tools under your user directory.
  2. To reuse tools, expand Reuse existing JDK / SDK, enter their root directories and choose Detect tools. JDK 17 or 21 must include javac. The SDK needs Platform 35 and Build Tools 35.0.0.
  3. Choose a tools directory to detect existing tools. To prepare missing tools, read and accept the Android SDK terms, then choose Prepare tools. Any remaining prerequisite appears below the controls. Studio reuses compatible JDKs and supplies command-line tools 13114758, SDK 35 and Build Tools 35.0.0. The project uses Gradle 8.9 and AGP 8.7.3.
  4. Wait for Tools ready and review the JDK, SDK and cache paths. Cancel preparation when needed; completed components remain usable. Correct network/path errors before detecting or preparing again.

Managed tools live in galcraft-android-0.1.0/ under the chosen directory, with default sdk/ and gradle-cache/ children. Reused tools retain their original paths. When managing the SDK yourself, follow Android SDK tool instructions to install the required versions and accept package licences.

4. Configure signing and environment variables

APK defaults to Explicit local test. AAB defaults to Author release signing. Local tests use an Android debug identity. For author signing, fill in:

FieldMeaning
Keystore pathFull path to your .jks or compatible keystore
Key aliasThe signing key’s alias in that keystore
Store password environment variableA variable name such as SPRING_STORE_PASSWORD
Key password environment variableA variable name such as SPRING_KEY_PASSWORD

Make both variables available to the local Studio service that builds the work. On Windows, set them in your account environment variables, stop the existing Studio service, reopen the terminal and start Studio. Alternatively, read them interactively in PowerShell 7 and launch the desktop app:

$env:SPRING_STORE_PASSWORD = Read-Host 'Keystore password' -MaskInput
$env:SPRING_KEY_PASSWORD = Read-Host 'Key password' -MaskInput
& 'C:\GalCraft\win-unpacked\GalCraft Studio.exe'

Replace the executable path with your installation. Stop the previous service for the same data directory under Local services first so the new service inherits this environment. For an npm installation, run galcraft-studio in that terminal. The form stores variable names; the build process reads their values.

5. Build and locate output

  1. Select a dedicated output directory. Choose Check and build, or use Check only to review issues first.
  2. Progress shows the Gradle task: assembleDebug for a test APK, assembleRelease for an author APK, or bundleRelease for AAB.
  3. Read signing mode, identity and result in the receipt. Find the final artifacts/<projectId>-<releaseVersion>.apk or .aab; the output also retains android-project/ for development.
  4. Install the APK on a target device and check reading and profile storage. Upload an AAB through your distribution platform. For Google Play upload keys and Play App Signing, follow the official guide.

Other targets: Web · Windows · iOS.