AndroidBuild Guide

Android Build & Signing

Practical guidance for generating signed AABs and installable APKs, with clear signing rules.

Google Play and Android status

Google Play builds (AAB) of website apps target API 36, the level Google Play requires for new apps and updates.
Source builds use the targetSdk set in your project.

Direct: generates an installable APK (best for sideload/testing).
Since September 30, 2026, certified Android devices in Brazil, Indonesia, Singapore and Thailand install apps from Google Play and six other stores only if a verified developer registered them; Google registers eligible Google Play apps automatically. Google says APKs people install directly are not affected yet, and plans to extend verification to them in 2027. Website apps created from 1 November 2026 get a key of their own that you can register; Preview APKs and website apps signed with our shared platform key can't be registered. Details: /docs/android-developer-verification.
Store: generates an AAB for Google Play (recommended for publishing).
Store builds are HTTPS-only and always release-signed: source projects with a key created for the project; website and Shopify apps with your uploaded keystore or, if you have not uploaded one, a key created for the app at its first build. An app created before 1 November 2026 without your keystore uses the platform key shared by many apps, and keeps it so installed copies keep updating.

Application ID: a unique reverse-domain package name (e.g. com.yourcompany.app).
Release signing: you can upload your own keystore when you create a Store app. Website and Shopify apps created from 1 November 2026 without one get a key made for the app; download a backup from the app's Signing page to use as your Google Play upload key or to register the app for Android developer verification. Free-plan previews built from 31 October 2026 do not lock the key, so you can still upload your own before the first release. An app on the shared platform key cannot be registered; email support to move it.
Versioning: set Version Name / Version Code in Project Settings.

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 platform or network faults refund the credit. A broken customer project does not. 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).