mobile-android-submission

You can publish an Expo app to Google Play by submitting it through EAS Build. This process generates an Android App Bundle (AAB), manages your signing keys, and uploads the release directly to the Play Console.

To submit your React Native app to the Google Play Store, you need a Google Play developer account, your local project path, and the application package name. The skill handles the remaining build and signing configurations.

Yes, you can integrate a custom keystore for your Android App Bundle submission. The skill automates default upload key handling while supporting optional custom keystore integration during the EAS build process.

Staged rollout for Expo Android releases distributes your app gradually across internal, alpha, beta, and production tracks. The skill submits your AAB and manages these rollout phases directly within the Play Console.

Configuring app.json and eas.json for production Android builds involves setting up your package name and build profiles. The skill guides this setup to ensure your project meets Play Console submission requirements.

Automated Google Play submission supports service-account authentication for uploading your AAB. This allows the skill to handle Play Console uploads, store listing setup, and staged rollouts without manual intervention.