Publish to Google Play
BuildStack can push a signed AAB straight to Google Play once you've connected a Play service account.
1. Create a Google 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.)
2. Add the service account to BuildStack
Open the project → Play credentials and upload the service-account JSON. It's sealed like every other credential and reused for each publish.
3. Build an AAB
Google Play requires the AAB format. Start a build with format AAB and a release variant, signed with your keystore (Android signing & keystores).
4. Publish
From the finished build (or the release flow), choose Publish to Google Play and the target track (internal, closed, open, or production). BuildStack uploads the AAB via the Play Developer API and reports the result.
Notes
- The app must already exist in the Play Console (first upload of a brand-new app
sometimes has to be done manually in the console; subsequent releases automate).
- Signing must match what Play expects — use the same keystore, or enrol in Play
App Signing.
- Track the outcome on the build's page; failures surface the Play API message.