AndroidBuild Guide
Android Build & Signing
Practical guidance for generating store-ready AABs and installable APKs with clear signing rules.
Store vs Direct
- Direct: generates an installable APK (best for sideload/testing).
- Store: generates an AAB for Google Play (recommended for publishing).
- Store builds are HTTPS-only and always release-signed — with our managed per-project key by default, or your uploaded keystore.
Required for Play Store
- Application ID: a unique reverse-domain package name (e.g. com.yourcompany.app).
- Release signing: your build is automatically signed with a managed per-project upload key. Optionally upload your own keystore in Project Settings → Android Signing to keep an existing signing identity.
- Versioning: set Version Name / Version Code in Project Settings.
Outputs
- Direct builds output: APK.
- Store builds output: AAB (and may also provide a test APK when available).
- Every artifact includes a SHA-256 for integrity verification.
Troubleshooting
- If you see “signing required”, upload your keystore and retry.
- If the build can’t download dependencies, retry the build — transient registry outages are common, and failed builds are auto-refunded. If it persists, check the build logs for the failing dependency and contact support.
- If your website uses HTTP, switch to Direct mode (or enable cleartext only for testing).