ci(play): upload signed AAB artifact for manual first upload#148
Conversation
The Google Play deploy keeps failing with an opaque "Google Api Error: Server error - Internal error encountered" — the known symptom of a brand-new Play app that has no first release yet (the Play Developer API rejects uploads until the first release is created manually in the Console). Save the signed AAB as a workflow artifact (if: always()) so the first release can be uploaded by hand; subsequent API deploys then work. Also guard the experimental/coroutine STL1011 define behind if(MSVC). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Set retention-days: 30 on the AAB artifact upload — the one-time manual-upload artifact only needs to persist until the first Play Console release is created; 90-day default wastes artifact quota. - Replace `if: always()` with `if: success() || failure()` so the step is skipped on workflow cancellation (always() fires on cancel too, producing a spurious warning about a missing AAB). https://claude.ai/code/session_012fCcD4T32mCWzkTgJxVMeR
Code Review — findings & fixes (ranked by severity)Medium — Commit message / PR description are inaccurateThe commit message ("guard MSVC coroutine define") and the PR description ("Guard the Low —
|
Why
The Google Play deploy job builds a valid signed AAB but the upload fails repeatedly with:
Two consecutive runs failed identically, the second failing even earlier (during "Preparing aab"). This is the well-known symptom of a brand-new Play app with no first release — the Play Developer API rejects uploads with an opaque 500 until the app's first release is created manually in the Console.
Change
daccord-playstore-aab,if: always()) so we can grab the exact signed bundle and do the one-time manual upload via the Play Console. API deploys work after that._SILENCE_EXPERIMENTAL_COROUTINE_DEPRECATION_WARNINGSdefine (from fix(windows): silence experimental/coroutine deprecation (STL1011) #147) behindif(MSVC).🤖 Generated with Claude Code