Skip to main content
Android requires a Firebase project for push notifications and, optionally, a Google Play service account for automated store submission. In Studio, go to Store Setup → Credentials → Android.

​
google-services.json

This file configures the Android app’s Firebase integration (FCM push notifications, analytics).

​
Getting the file

  1. Open Firebase Console and select (or create) your project.
  2. Go to Project Settings → General → Your apps.
  3. Click Add app and choose the Android icon.
  4. Enter your Android package name (must match the one in Studio exactly).
  5. Register the app and download google-services.json.
If you have both a test and a production Android app in the same Firebase project, add both package names to the Firebase project first. The downloaded google-services.json will contain both clients — one file covers both.

​
Uploading to Studio

Upload the google-services.json file in the google-services.json field.

​
Service Account Admin SDK JSON

Required for EAS / Expo to relay Firebase Cloud Messaging v1 push notifications.

​
Getting the file

  1. In Firebase Console, go to Project Settings → Service accounts.
  2. Click Generate new private key.
  3. Confirm and download the JSON file.

​
Uploading to Studio

Upload the service account JSON in the Service Account Admin SDK JSON field.

​
Google Play API

Required for automated submission to the Play Store (optional if you prefer to upload manually).

​
Getting the credentials

  1. Open Google Play Console and go to Setup → API access.
  2. Link to a Google Cloud project (or create one).
  3. Create a service account with Release manager permissions.
  4. Download the service account JSON key.

​
Uploading to Studio

Upload the service account JSON in the Google Play Service Account field.

​
Android app signing

Android builds must be signed with a keystore. Studio and EAS manage the keystore for you:
  • On the first build, EAS generates a keystore and stores it securely
  • Subsequent builds reuse the same keystore automatically
  • You can also upload your own keystore if you already have one (e.g. migrating from an existing app)
Do not lose your keystore. If you need to update an existing Play Store listing, your update must be signed with the same keystore as the original release. EAS stores it securely but you should also keep a backup.