Lesson 13 of 19Article18 min
GCP & Google Play Console Setup
Every Android release flows through Google Play Console. Automated uploads require a GCP service account linked to your Play Developer account. Manual first upload is recommended to understand the console before automating.
Android release prerequisites
Every Android release flows through Google Play Console. Automated uploads require a GCP service account linked to your Play Developer account. Manual first upload is recommended to understand the console before automating.
Play Console + GCP setup flow
Step-by-step setup
- Create Google Play Developer account at play.google.com/console ($25 one-time fee).
- Create GCP project (or use existing) at console.cloud.google.com.
- Play Console → Setup → API access → Link the GCP project.
- GCP → IAM → Create service account (e.g. play-deploy-bot).
- Play Console → Users and permissions → Invite service account email.
- Grant: Release to testing tracks, View app information (not financial data).
- GCP → Service account → Keys → Add key → JSON → download once securely.
- Store JSON in GitHub Secret; in CI write to temp file with chmod 600.
CI: write Play Store key from secret
- name: Decode Play Store key
run: |
echo "${{ secrets.PLAY_STORE_JSON_KEY }}" > play-key.json
chmod 600 play-key.json
env:
PLAY_STORE_JSON_KEY: ${{ secrets.PLAY_STORE_JSON_KEY }}Before first upload checklist
- App listing: title, description, screenshots (phone + tablet), feature graphic.
- Content rating questionnaire completed.
- Data safety form filled (data collection, sharing, encryption).
- Privacy policy URL hosted and linked.
- Target API level meets Play requirements (check current Android target SDK policy).
- Play App Signing enabled (recommended for all new apps).