Publish Your React Native & Expo (EAS) App to Google Play Without Review Delays
Whether you build with Expo Application Services (`eas build --platform android`) or bare React Native Gradle workflows, PlayGate takes your production `.aab` and ships it straight to Google Play Production—bypassing the 14-day closed testing gate.
- •Default Expo modules automatically adding `RECORD_AUDIO`, `READ_EXTERNAL_STORAGE`, or `SYSTEM_ALERT_WINDOW` unless explicitly blocked in `app.json` (`android.blockedPermissions`).
- •Expo Updates / OTA configuration or `expo-notifications` Device ID transmission left undeclared in the Google Play Data Safety section.
- Set `android.package` in `app.json` / `app.config.ts` to a unique `com.company.app` identifier.
- Add unused sensitive permissions to `android.blockedPermissions` in `app.json` before running `eas build`.
- Download the signed `.aab` artifact from your EAS Build dashboard and upload it on `/order`.
1. How to Strip Unwanted Permissions in Expo `app.json` Before Uploading
Expo SDK plugins often bundle broad Android permissions by default. By configuring `android.blockedPermissions` in your `app.json` and letting our pre-flight team inspect your EAS `.aab` bundle before submission, you avoid 'Photo and Video Permissions' and 'Foreground Service' rejections.
2. Keep Your EAS Keystore & Accept Transfer in 24 Hours
EAS manages your upload keystore securely in your Expo account. You simply provide the `.aab` output from EAS Build, we pass Google Play review on our established console, and transfer the approved app directly into your Google Play account.
React Native & Expo (EAS) Publishing FAQ
Does Google Play App Transfer break EAS Submit or future Expo updates?
Not at all. Because Google Play App Signing preserves the app signing key and your upload key remains in your EAS account, future `eas submit` releases work seamlessly inside your own Play Console after transfer.