Proper Android release builds using Orbital CLI and signing #803

Merged
SakulFlee merged 12 commits from fix/orbital-cli-android-release-builds into main 2026-09-22 22:24:42 +00:00
Owner
No description provided.
Add keystore_path, keystore_password, key_alias, and key_password fields
to AndroidConfig for signing release APKs. This allows users to configure
signing in their Orbital.toml file.
Update the APP_BUILD_GRADLE template to include signing configuration
for release builds. The template now uses placeholders for keystore path,
password, key alias, and key password. The keystore directory is created
during project generation if signing is configured.
Add functions to ensure a keystore exists for signing release APKs.
If no keystore is configured in Orbital.toml, a debug keystore is
automatically generated using keytool. The keystore is created in the
Android/app/keystore/ directory.
Update the update_android_project function to replace signing configuration
placeholders in the build.gradle file. This ensures the correct keystore
path, password, key alias, and key password are used for signing release
APKs.
Add commented-out signing configuration fields to the Orbital.toml template.
This helps users understand how to configure signing for release APKs.
Add commented-out signing configuration fields to the project's Orbital.toml
to document the new signing feature for release APKs.
When building a release APK without a configured keystore, the CLI now
prompts the user to generate a debug keystore. If the user declines,
the build continues but the APK will not be signed. In non-interactive
mode (CI), a debug keystore is auto-generated.

Also updates Orbital.toml with the keystore path after generation.
chore: update Cargo.lock with libc dependency
Some checks failed
Lint / lint (pull_request) Failing after 4m54s
4987575e45
Sign in to join this conversation.
No description provided.