Hiprup

What is the typical release process for a React Native app on both stores?

Releasing a React Native app to Google Play and the App Store is a four-stage pipeline that production teams typically automate end-to-end.

1. Build artifacts:

  • Android: ./gradlew bundleRelease → AAB (App Bundle, required by Play Store) or assembleRelease → APK.

  • iOS: xcodebuild archive + exportArchive → IPA.

  • Or use EAS Build (cloud) — eas build --platform all --profile production.

2. Code signing:

  • Android: upload keystore (`.keystore` file, keep it secret); configure in android/gradle.properties.

  • iOS: Apple Developer cert + provisioning profile; App Store Connect API key for automation.

  • Match (Fastlane) or EAS Credentials handle signing securely in CI.

3. Store upload + review:

  • Google Play Console — internal → closed → open → production tracks; review typically < 24h.

  • App Store Connect — TestFlight (internal + external) → submit for review; review typically 1-3 days.

  • Privacy declarations: Apple Privacy Manifest, Google Play Data Safety form.

  • Automate via Fastlane (deliver, supply) or EAS Submit.

4. Post-release:

  • OTA updates for JS-only fixes — EAS Update or Shorebird; no store review.

  • Crash monitoring with Sentry; phased rollouts on Play; staged rollout on App Store.

Frame this as a pipeline, not a checklist. Strong answer covers four stages: (1) build artifacts (AAB/IPA), (2) signing + provisioning, (3) store upload (Google Play Console + App Store Connect), (4) post-release (OTA for JS-only fixes, store update for native changes).

Bonus: mention EAS Submit, Fastlane, and TestFlight / internal testing tracks — these are the tools senior RN engineers automate with.

What is the typical release process for a React Native app on both stores? | Hiprup