Mobile App Development

Deploy Expo React Native App to App Store & Google Play — Complete Guide

Step-by-step guide to deploy your Expo React Native app to the Apple App Store and Google Play Store using EAS Build and EAS Submit. Covers app.json, eas.json, internal testing, submission, and common rejection fixes.

By Published: Reading time: 14 min read Level: BEGINNER
Developer deploying a React Native Expo app to the Apple App Store and Google Play Store

Shipping your first Expo React Native app to the App Store and Google Play is one of those milestones that feels both exciting and intimidating. This end-to-end guide walks you through every step — from configuring your app.json to clicking "Submit for Review" — with the exact commands, field values, and common pitfalls you need to avoid.

Applies to: Expo SDK 51+, EAS CLI 12+


Prerequisites

Before you begin, make sure you have the following:

Requirement Details
Expo account Sign up at expo.dev
EAS CLI yarn global add eas-cli
Apple Developer account $99/year at developer.apple.com
Google Play Developer account $25 one-time at play.google.com/console
Working Expo project An Expo-managed React Native app

Note: Never use npm to install EAS CLI globally in projects that use Yarn as their package manager. Use yarn global add eas-cli instead, or run npx eas-cli@latest to avoid any global install entirely.


Step 1 — Configure app.json

app.json is the single source of truth for your app's identity on both stores.

{
  "expo": {
    "name": "Your App Name",
    "slug": "your-app-slug",
    "version": "1.0.0",
    "orientation": "portrait",
    "icon": "./assets/icon.png",
    "userInterfaceStyle": "light",
    "ios": {
      "icon": "./assets/icon.png",
      "supportsTablet": false,
      "bundleIdentifier": "com.yourcompany.yourapp",
      "buildNumber": "1",
      "infoPlist": {
        "ITSAppUsesNonExemptEncryption": false,
        "NSCameraUsageDescription": "Used to take a photo for your profile picture.",
        "NSPhotoLibraryUsageDescription": "Used to select a photo for your profile picture.",
        "NSPhotoLibraryAddUsageDescription": "Used to save receipts to your photo library."
      }
    },
    "android": {
      "adaptiveIcon": {
        "foregroundImage": "./assets/adaptive-icon.png"
      },
      "package": "com.yourcompany.yourapp",
      "versionCode": 1,
      "googleServicesFile": "./google-services.json",
      "permissions": ["android.permission.CAMERA"]
    },
    "plugins": [
      "expo-font",
      ["expo-splash-screen", { "image": "./assets/splash-icon.png", "backgroundColor": "#ffffff", "resizeMode": "contain", "imageWidth": 200 }],
      ["expo-image-picker", { "photosPermission": "Used to select a photo for your profile picture.", "cameraPermission": "Used to take a photo for your profile picture." }],
      ["expo-notifications", { "icon": "./assets/notification-icon.png", "color": "#ffffff", "defaultChannel": "default", "sounds": [] }]
    ],
    "extra": { "eas": { "projectId": "your-eas-project-id" } },
    "owner": "your-expo-username"
  }
}

Key Fields Explained

Field Description
name Display name users see on the Home Screen
slug URL-safe identifier used by EAS
version Human-readable version shown in stores (e.g. 1.0.0)
bundleIdentifier iOS unique ID — format: com.company.appname
package Android unique ID — same reverse-domain format
versionCode Android integer — must increase with every upload
buildNumber iOS integer string — must increase with every upload
ITSAppUsesNonExemptEncryption Set false if you don't use custom encryption (standard HTTPS does not count)

⚠️ Never reuse bundleIdentifier or package from another app. Once registered in a store, these are permanent identifiers for your app's entire lifetime.


Step 2 — Configure eas.json

eas.json controls how EAS Cloud builds and submits your app for each environment.

{
  "cli": {
    "version": ">= 12.0.0",
    "appVersionSource": "remote"
  },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal",
      "env": {
        "EXPO_PUBLIC_API_BASE_URL": "https://your-dev-api.com",
        "EXPO_PUBLIC_ENV": "development"
      }
    },
    "preview": {
      "distribution": "internal",
      "android": { "buildType": "apk" },
      "ios": { "simulator": false },
      "env": {
        "EXPO_PUBLIC_API_BASE_URL": "https://your-staging-api.com",
        "EXPO_PUBLIC_ENV": "preview"
      }
    },
    "production": {
      "autoIncrement": true,
      "android": { "buildType": "app-bundle" },
      "ios": { "simulator": false },
      "env": {
        "EXPO_PUBLIC_API_BASE_URL": "https://your-production-api.com",
        "EXPO_PUBLIC_ENV": "production"
      }
    }
  },
  "submit": {
    "production": {
      "android": {
        "serviceAccountKeyPath": "./play-console-service-account.json",
        "track": "internal",
        "releaseStatus": "draft",
        "changesNotSentForReview": true
      },
      "ios": {
        "appleId": "your@email.com",
        "ascAppId": "1234567890",
        "appleTeamId": "XXXXXXXXXX"
      }
    }
  }
}

Where to find these values

Field Where to find
ascAppId App Store Connect → Your App → App Information → Apple ID
appleTeamId developer.apple.com → Membership → Team ID
serviceAccountKeyPath Google Play Console → Setup → API access → Service account JSON

💡 autoIncrement: true in your production profile tells EAS to automatically increment both versionCode (Android) and buildNumber (iOS) before each build. You never need to manually bump these numbers again.


Step 3 — Build the App with EAS

Login to EAS

eas login

Initialize EAS in your project (first time only)

Running this command generates a base eas.json automatically:

eas build:configure

Trigger a production build

# Build for both platforms simultaneously
eas build --platform all --profile production

# Android only
eas build --platform android --profile production

# iOS only
eas build --platform ios --profile production

💡 EAS builds run entirely in Expo's cloud — you do not need Xcode or Android Studio installed on your local machine.

Monitor your build

eas build:list

Step 4 — Google Play Store Deployment

4.1 — Create the App

  1. Go to Google Play Console
  2. Click Create app
  3. Fill in App name, Default language, App or game, Free or paid
  4. Accept policies → Create app

4.2 — Fill in Store Listing

Navigate to Main store listing and complete:

  • App name (max 30 chars)
  • Short description (max 80 chars)
  • Full description (max 4000 chars)
  • Screenshots (min 2, max 8 per device type)
  • App icon (512×512 PNG — no rounded corners, Play Console applies the mask)
  • Feature graphic (1024×500 PNG)

4.3 — Content Rating

  1. Go to Policy → App content → Content rating
  2. Click Start questionnaire and answer honestly
  3. Submit → rating is assigned automatically

4.4 — App Privacy (Photo & Video Permissions)

If your app requests READ_MEDIA_IMAGES on Android 12 and below, justify it under Policy → App content → Photo and video permissions.

Best practice: Use expo-image-picker instead. On Android 13+, it uses the Android Photo Picker and does not require READ_MEDIA_IMAGES at all.

4.5 — Internal Testing

  1. Go to Testing → Internal testing → Create new release
  2. Upload your .aab file (produced by eas build)
  3. Add release notes → Save and roll out

4.6 — Move to Production

  1. Production → Create new release
  2. Add the same .aab (no need to rebuild)
  3. Fill release notes → Submit for review

Step 5 — Apple App Store Deployment

5.1 — Register Bundle ID

  1. developer.apple.com → Certificates, Identifiers & Profiles → Identifiers → +
  2. Select App IDs → App
  3. Set Bundle ID: com.yourcompany.yourapp (Explicit)
  4. Continue → Register

5.2 — Create App in App Store Connect

  1. appstoreconnect.apple.com → Apps → + → New App
  2. Fill: Platform (iOS), Name, Primary Language, Bundle ID, SKU, User Access
  3. Click Create

5.3 — Fill App Information

  • Subtitle (max 30 chars)
  • Category: Most accurate primary category
  • Privacy Policy URL: Required for all apps
  • Support URL

5.4 — Fill Version Information

  • Promotional Text (max 170 chars): Updateable without review
  • Description (max 4000 chars)
  • Keywords (max 100 chars total): Comma-separated
  • Copyright: 2026 Your Company Name

5.5 — App Privacy (Data Collection)

If your app has user accounts, select "Yes, we collect data" and declare:

Data Type Declare if...
Name Users have profiles
Email Address Users register with email
Phone Number OTP or phone login
User ID Backend assigns unique IDs
Physical Address Users enter delivery addresses
Purchases App has in-app purchases
Device ID You send push notifications

For each declared type: Purpose → App Functionality, Linked to user → Yes, Tracking → No.

5.6 — Screenshots (Required!)

Device Resolution Minimum
iPhone 6.9" (iPhone 16 Pro Max) 1320×2868 px 3 screenshots
iPhone 6.5" (iPhone 13/14 Pro Max) 1284×2778 px 3 screenshots
iPad 13" Only if supportsTablet: true 3 screenshots

💡 Use your Simulator or tools like Rotato or AppMockUp for polished screenshots.

5.7 — App Review Information

⚠️ Most common rejection reason for apps with OTP login.

  • Sign-In Required: ✅ if app needs login
  • Username / Phone: Provide real test credentials
  • Password / OTP: Must be a fixed static OTP (e.g. 444444) for the reviewer's test number

Ask your backend team to whitelist a specific test phone number with a fixed OTP. Remove after approval.

  • Notes: Explain any non-obvious flows

5.8 — Version Release

For first submissions, select "Automatically release this version".

5.9 — Submit for Review

Click Add for Review → Submit to App Review

Apple's review typically takes 24–48 hours for first-time submissions.


Step 6 — Submit via EAS

# Submit to both stores
eas submit --platform all --profile production

# Android only
eas submit --platform android --profile production

# iOS only
eas submit --platform ios --profile production

Common Mistakes & Fixes

❌ Same versionCode uploaded twice (Android)

Fix: Increment versionCode before each build, or use "autoIncrement": true in eas.json.

❌ READ_MEDIA_IMAGES permission blocked by Google Play

Fix: Remove it from app.json. Use expo-image-picker — it uses Android Photo Picker on Android 13+ with no permission needed.

❌ Apple rejects because reviewer cannot log in

Fix: Whitelist a test phone number with a fixed static OTP in your backend. Provide it in App Review Information.

❌ Permission strings describe features not in this build

Fix: NSCameraUsageDescription and similar strings must match only the current build's features. Mentioning unimplemented features triggers Guideline 2.1 rejection.

❌ Missing Privacy Policy URL

Fix: Generate one at privacypolicygenerator.info and host it publicly.

❌ No account deletion option (Apple Guideline 5.1.1)

Fix: Apple requires an in-app "Delete Account" option for any app with user accounts.

❌ supportsTablet: true but no iPad screenshots

Fix: Set supportsTablet: false or upload iPad 13" screenshots.


Checklist Before Submitting

Android ✅

  • Unique package name
  • versionCode incremented (or autoIncrement enabled)
  • google-services.json in project root
  • App icon 512×512 PNG
  • Feature graphic 1024×500 PNG
  • At least 2 screenshots
  • Content rating questionnaire completed
  • Privacy policy URL added
  • READ_MEDIA_IMAGES removed or justified
  • Release notes added

iOS ✅

  • Bundle ID registered in Apple Developer Portal
  • buildNumber incremented (or autoIncrement enabled)
  • ITSAppUsesNonExemptEncryption: false in infoPlist
  • All NS*UsageDescription strings accurate
  • App created in App Store Connect
  • 6.9" and 6.5" screenshots uploaded (min 3 each)
  • Privacy policy URL added
  • Data collection accurately declared
  • App Review test credentials provided
  • Fixed test OTP working
  • In-app account deletion implemented
  • Keywords filled (max 100 chars)
  • Description and subtitle filled

Push Notifications Setup

Android

  • Add google-services.json to project root (Firebase Console → Project Settings → Your Apps)
  • Add expo-notifications plugin to plugins in app.json
  • No extra permissions array entry needed

iOS

  • Run eas build — it prompts to configure APNs Push Notification Keys
  • Select "Yes" when asked
  • One APNs key works across all apps under the same Apple Team

Versioning Strategy

Release Type version versionCode / buildNumber
First release 1.0.0 1
Bug fix 1.0.1 2
New feature 1.1.0 3
Major update 2.0.0 4

💡 With "autoIncrement": true, EAS remotely manages versionCode and buildNumber. You only update version manually when you want to change the store-displayed version string.


Useful Commands

eas login
eas build:configure
eas build --platform all --profile production
eas build:list
eas submit --platform all --profile production
eas credentials

Resources