This guide walks you through the practical steps of releasing a React Native app to both the Apple App Store and Google Play Store. You’ll learn the exact order of operations, what to prepare, and how to avoid common pitfalls. Before starting, you need a completed app, an Apple Developer account ($99/year), a Google Play Developer account ($25 one-time), and access to your app’s signing keys.
What You’ll Need
- Apple Developer Program membership
- Google Play Console account
- Node.js and npm/yarn installed
- Xcode (latest stable version) for iOS builds
- Android Studio for Android builds
- App icons in all required sizes (or a 1024×1024 master icon)
- Privacy policy URL (required by both stores)
- App store screenshots (6.9″ and 6.5″ for iPhone, 12.9″ iPad, plus Android phone and tablet sizes)
Step-by-Step
- Bump the version numbers. In
package.json, updateversionto your release version (e.g., 1.0.0). For iOS, openios/YourApp.xcodeprojin Xcode, select the app target, go to the General tab, and set Version (e.g., 1.0.0) and Build (e.g., 1). For Android, editandroid/app/build.gradle: setversionCodeto an integer (e.g., 1) andversionNameto the same string (e.g., “1.0.0”). Increase the build/versionCode by 1 for every subsequent upload. - Configure app icons and splash screens. Use a tool like
npx react-native-assetor manually place icons inios/YourApp/Images.xcassetsandandroid/app/src/main/res/mipmap-*folders. For splash screens, considerreact-native-bootsplashor configure the native splash in both platforms. Ensure the icon has no transparency (iOS rejects transparent icons). - Set the display name. In Xcode, under Info.plist, set
CFBundleDisplayNameto the exact name you want under the app icon. For Android, setandroid:labelinAndroidManifest.xmlto the same name. - Enable App Transport Security (ATS) exceptions if needed. If your app loads HTTP (non-HTTPS) content, add exceptions to
Info.plistunderNSAppTransportSecurity. For production, prefer HTTPS; exceptions are only for development or specific domains. - Prepare Android signing keystore. Generate a keystore file:
keytool -genkey -v -keystore your-app.keystore -alias your-app-alias -keyalg RSA -keysize 2048 -validity 10000. Store this file securely—you cannot recover it. Then createandroid/key.propertieswith storeFile, storePassword, keyAlias, and keyPassword. Reference this inbuild.gradleundersigningConfigs. - Build the Android release APK/AAB. Run
cd android && ./gradlew bundleReleaseto create an AAB (recommended for Play Store). The output is inandroid/app/build/outputs/bundle/release/app-release.aab. Test this build on a physical device before uploading. - Build the iOS release archive. In Xcode, select “Any iOS Device (arm64)” as the destination, then go to Product > Archive. After archiving, open the Organizer window, select your archive, and click “Distribute App.” Choose “App Store Connect” and follow the prompts. This uploads the build to App Store Connect.
- Set up App Store Connect listing. Go to App Store Connect > My Apps > create a new app. Fill in the description, keywords, support URL, marketing URL (optional), and privacy policy URL. Upload screenshots (6.7″ and 6.5″ for iPhone, 12.9″ for iPad if universal). Add app review notes if you use demo accounts or special configurations.
- Set up Google Play Console listing. In Play Console, create a new app. Complete the “Store listing” section: short description, full description, app icon, feature graphic (1024×500), screenshots, and app category. Provide the privacy policy URL. Set content rating by completing the questionnaire.
- Upload the Android AAB. In Play Console, go to “Production” under “Release” and click “Create new release.” Upload your
.aabfile, add release notes, and save. Then review and roll out the release to a closed test track first (recommended) or directly to production. - Submit iOS for review. In App Store Connect, select the build you uploaded, set the version, and click “Submit for Review.” Answer the export compliance question (usually “No” unless you use encryption beyond HTTPS). Wait for review—typically 24-48 hours but can take longer.
- Monitor and respond. Once submitted, watch for status changes. If rejected, read the reason, fix the issue, and resubmit. For Android, the review is usually faster (hours to a few days). After approval, your app goes live—you can then promote it in the store listing.
Common Mistakes
- Forgetting to increment versionCode/build number. Every Android upload must have a higher versionCode; iOS requires a new build number. Reusing the same number causes an upload error.
- Using a debug keystore for release. The debug keystore is not accepted by the Play Store. Always use a dedicated release keystore and back it up.
- Missing privacy policy. Both stores require a valid, publicly accessible privacy policy URL. Apps collecting any user data (even email) must link it.
- Ignoring iOS screen sizes. Submitting only one screen size can lead to rejection. Provide all required screenshot sizes or mark the app as iPhone-only with the correct sizes.
- Hardcoding environment URLs. Ensure your release build points to production APIs, not localhost or staging. Use environment variables or build-time configuration.
- Not testing the release build. Release builds behave differently (minified, no dev menu). Always test the exact binary you upload on a physical device.
Tips
- Use a CI/CD pipeline. Services like GitHub Actions, Bitrise, or Fastlane can automate builds and uploads, reducing manual errors.
- Set up internal testing first. For both stores, use internal/closed tracks to test with a small group before public release.
- Prepare release notes in advance. Write clear, user-facing notes that highlight new features and bug fixes. Keep them concise.
- Check for missing permissions. Android will warn about unused permissions; iOS will ask at runtime. Only request what you need.
- Use App Store Connect API for automation. If you automate, use the API to upload builds and manage metadata.
- Keep a changelog. Track what changed between versions—this helps with release notes and debugging.
Troubleshooting
- iOS archive fails with “No signing certificate found.” Open Xcode > Preferences > Accounts, add your Apple ID, and download the distribution certificate. Ensure your team is selected in the target’s Signing & Capabilities tab.
- Android build fails with “Keystore was tampered with, or password was incorrect.” Double-check the passwords in
key.properties. If you lost the keystore, you must create a new one and change the package name (or use Play App Signing to upload a new key). - App Store Connect says “No builds available.” Wait 10-15 minutes after uploading; processing takes time. Also verify the build’s version and build number match the listing.
- Google Play rejects the AAB for “App Bundle contains invalid signature.” Rebuild with the correct release keystore. Check that
signingConfigis applied to the release build type. - App crashes on launch in release but works in debug. Check for missing ProGuard rules. Add
-keeprules for third-party libraries inproguard-rules.pro. For iOS, check for missing frameworks or bitcode issues. - Review rejection for “Incomplete information.” Fill in every required field, including demo account credentials if your app requires login. Provide a video of the app in action if needed.
Frequently Asked Questions
How long does app review take?
iOS review typically takes 24-48 hours, but can extend to a week during busy periods. Android review is usually faster, often under 24 hours, but can take up to 7 days for new accounts.
Can I release the same app on both stores simultaneously?
Yes, but you may want to stagger releases by a day to handle any store-specific issues. There’s no rule against simultaneous release.
Do I need a paid Apple Developer account for testing?
For local testing on a device, a free account works with limitations. To distribute via TestFlight or the App Store, you need the $99/year paid membership.
What is the difference between an APK and an AAB?
APK is the installable file; AAB is a bundle that Google Play uses to generate optimized APKs per device. Always upload AAB to Play Store; APK is fine for sideloading.
How do I update my app after release?
Bump the version code/name, rebuild, and upload the new binary. For iOS, create a new version in App Store Connect. For Android, create a new release in the same track.
What if my app gets rejected for a bug?
Fix the bug, rebuild, and resubmit. For iOS, you can also use “App Store Connect” to request an expedited review if the issue is critical (e.g., security vulnerability).
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix msmpeg2vdec.dll Errors in Windows
- How to Update Sonos App and Speakers
- Unlock iPad Without Apple ID: Is It Possible?
- iOS 18 WhatsApp Notifications Not Working? Fix
- Fix Windows Cannot Locate Suitable Printer Driver
- Monster Hunter World PC Crash: Solved?