Publish to Google Play
BuildStack can build a signed AAB and push it to a Google Play track in the same step, using your Play service account.
Publishing to Play is a build option, not a button on a finished build. You turn it on _before_ you build (Production build type). The Distribute/ Release button on a finished build is a different feature; it shares an install link with your own testers, not Google Play. See Distribute to testers.
1. Connect a Play service account
In the Google Play Console, create a service account with permission to manage releases and download its JSON key (Play Console → Users and permissions → invite the service account; Google Cloud → create the key).
Then open the project → Credentials → Play publishing and upload the JSON. It's sealed like every other credential. Once saved, use Test connection (enter your applicationId) to confirm the account can sign in _and_ has access to your app; do this before your first publish so you don't wait on a build to find out.
2. Set the version code
Every upload to Play must have a higher versionCode than the last one already on Play (across all tracks). On the build form, set the Version code accordingly; see Versioning your app. Getting this wrong is the most common publish failure ("version code N has already been used").
3. Build with Publish on
On the Build tab:
- Choose Production (a signed release that needs your keystore, see
- Set Format to AAB (Play requires it).
- Turn on Publish to Google Play and enter your applicationId
(e.g. com.acme.app).
- Set the Version code (and name), then Build & publish.
The build runs, signs the AAB with your upload key, and uploads it to the Internal track as a draft. The build page shows the result ("Uploaded v9 to internal…").
4. Finish the release in Play Console
The upload is a draft; nothing reaches testers until you complete it:
Play Console → Testing → Internal testing → your draft → Review release → Start rollout. From there you can promote Internal → Closed/Open/Production.
Notes
- The app must already exist in Play, with at least one release done manually
in the console; the Play API can't create the first release of a new app.
- Signing must match what Play expects: sign with your upload key, or enrol in
Play App Signing. A mismatch is rejected with "signed with the wrong key" (see Troubleshooting).
- Today BuildStack publishes to the Internal track as a draft; use Play Console
to promote to other tracks.