CI: build App Bundle for Play Store uploads instead of APK - #684
Merged
Mansimran Singh (Mansimran-Singh) merged 1 commit intoAug 19, 2026
Merged
Conversation
Play rejected both release pipelines' uploads with "Cannot replace a bundle of version code 31 with an APK" — the app already has a bundle published at that version code, and Play won't accept a raw APK once a bundle exists for a given versionCode. Switch the Play Store upload step in each workflow to bundleRelease's .aab output; leave the APK build (used by the Firebase distribution step and the GitHub release attachment) as-is since those already work. Related to #626.
Mansimran Singh (Mansimran-Singh)
requested review from
Michael Gonzalez (MicGon7) and
dlucci-wt
as code owners
August 19, 2026 15:47
Mansimran Singh (Mansimran-Singh)
deleted the
feature/626/play-store-aab-upload
branch
August 19, 2026 16:01
12 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pre-release-upload.yml(runs on every merge tomain) has failed its Play Store upload step on both of its real runs so far, withCannot replace a bundle of version code 31 with an APK.— the app already has a bundle published at that version code, so Play rejects a raw APK.ps-release.yml(tag-triggered production pipeline) andpre-release-upload.yml(closed-testing/alphatrack pipeline) to runbundleReleasealongsideassembleRelease, and point the Play Store upload step at the resulting.aabinstead of the.apk.Ticket
Related to #626
Type of Change
Testing
No unit-testable logic changed — this is a CI workflow config fix. Confirmed via
gh run viewon the two prior realpre-release-upload.ymlruns (2026-08-08, 2026-08-18) that both failed at the identicalCannot replace a bundle...step, and confirmedbundleRelease/app/build/outputs/bundle/release/app-release.aabis the correct AGP-generated task/path for this project's build config. The actual end-to-end validation (does the fixed upload succeed against Play) will happen automatically on the next merge tomain, sincepre-release-upload.ymlis already wired intobuild.yml— no extra trigger needed.Checklist
./gradlew testDebug)