Back to Guides

Google Play Deployment Guide

Configure automatic Android app deployments to Google Play Console. Set up once, and every build automatically uploads to your chosen testing track or production.

Prerequisites

Before configuring Google Play deployment:

  • Google Play Developer Account - One-time $25 registration fee
  • App Created in Google Play Console - Your app must exist in Play Console before connecting
  • Google Cloud Project - With Google Play Android Developer API enabled
  • Service Account JSON - With Release Manager permissions in Google Play Console

Configuration Steps

  1. 1

    Create Service Account

    In Google Cloud Console, navigate to IAM & Admin → Service Accounts. Create a new service account or use an existing one.

    Note the service account email address - you'll need it for the next step.

  2. 2

    Generate JSON Key

    In the Service Account details, go to Keys → Add Key → Create new key → Select JSON format.

    Download the JSON file immediately - this is your only chance to download it.

  3. 3

    Grant Play Console Access

    In Google Play Console, go to Setup → API access. Find your service account email and grant it Release Manager permissions.

    Release Manager allows uploading builds but not publishing to production (you maintain control).

  4. 4

    Upload JSON to ExpoDeploy

    During onboarding or in project settings, upload the complete JSON key file. ExpoDeploy extracts the necessary credentials and stores them encrypted.

  5. 5

    Configure Deployment Settings

    Choose which testing track to upload to (internal, alpha, beta) and enable automatic deployments for your production branch.

  6. 6

    Test Deployment

    Push code to trigger a build. After completion, check Google Play Console → Release → Testing to verify the AAB was uploaded successfully.

Automatic Deployment Process

When enabled, ExpoDeploy automatically:

  • • Uploads AAB files to your configured testing track after successful builds
  • • Handles version code and version name management
  • • Creates new releases or updates existing ones
  • • Sends notifications when uploads complete
  • • Provides deployment logs for troubleshooting

After upload, you can review the release in Google Play Console, test with internal testers, and promote to production when ready. ExpoDeploy never publishes to production automatically - you maintain full control.

Important Notes

  • Version Codes: Each upload must have a higher version code than the previous release
  • Testing Tracks: Start with internal testing, then promote to alpha/beta before production
  • Review Process: First-time apps require manual review in Play Console before going live
  • Permissions: Release Manager role allows uploads but not production publishing (security best practice)