How to publish a React Native app on the App Store and Google Play? (2026 checklist)

The problem: the app is “done”, but Apple says no

Engineering signs off, marketing is booked, you upload to App Store Connect and the status is Rejected. Common causes: vague camera permission copy or a login screen that breaks Apple rules (for example missing Sign in with Apple when social logins exist).

At GMI Software, with 16+ years and 120+ projects, we treat store submission as a technical and policy audit, not paperwork. Launch readiness sits inside DDT (Discovery, Design & Technology) and we own the outcome.

App Store vs Google Play - how reviews differ

Know the two philosophies before you freeze scope:

• Apple App Store: Human reviewers exercise the build end-to-end. UX quality matters, not only crashes. First response often lands in 24-48 hours, but rejection loops can stretch a week.
• Google Play: Heavy automated scanning plus privacy rules. Since roughly 2024 many new accounts must complete closed testing (for example 20 testers for 14 days) before production access.

Technical checklist: preparing React Native for release

A great roadmap fails if the reviewer hits a crash on first launch. Before we ship, we run checks such as:

1. Expo EAS setup: `eas build` produces .aab and .ipa from a consistent cloud environment instead of “works on my laptop” certificates.
2. Performance (Hermes and logs): Hermes stays on, production bundles drop stray `console.log` calls to reduce noise and battery burn.
3. Permissions copy: Info.plist and AndroidManifest.xml carry precise, user-facing reasons (for example location to show the nearest drop-off points - the same pattern we proved on EMKA Mobile).
4. Certificates and keystores: Apple provisioning profiles and Android keystores are generated, stored and handed over securely. Losing an Android keystore blocks updates for that package name.
5. Reviewer demo accounts: Logged-in experiences (for example Berg System-style CRM apps) need working credentials or reviewers reject within hours.

Top rejection reasons we see from Apple and Google

Reading **App Store Review Guidelines** and Play policies saves launch week:

• Missing Sign in with Apple when Google or Facebook login exists.
• Screenshot/device mismatches, such as iPhone notch shots uploaded to an iPad listing.
• “Beta” or “Test” strings in production UI. Use TestFlight or Play internal tracks instead.
• External payments for digital goods: Digital courses or subscriptions usually require in-app purchase (Apple’s 15-30% cut). External gateways such as Stripe with MedusaJS are typically fine for physical goods and real-world commerce flows.

Less launch stress with GMI Software

Leaders need predictable delivery. We are the only Polish software house offering a fixed-price guarantee after DDT for building and publishing React Native apps.

The SFD app shipped on both platforms from one codebase, handled heavy session load and earned a Mobile Trends Awards 2025 nomination. You keep the source, avoid vendor lock-in, and get hands-on help with developer accounts and build pipelines.