Skip to content
Tutorials Center
My learning

Topics

Lesson 30 of 38 ยท EAS Build and Updates

Submitting to the App Store and Google Play

Release an Expo app: store accounts, listing assets, eas submit for iOS and Android, TestFlight and Play tracks, review rules, staged rollouts and a release checklist.

A production build is a file on your disk or on Expo's servers. Users cannot install it until it passes through App Store Connect (iOS) or the Google Play Console (Android). Getting there involves accounts, store listings, privacy forms and review. The code part is small; the preparation is where beginners lose days.

This lesson walks the whole path: what to prepare, how eas submit uploads your build, how test tracks work, and how to avoid the most common rejections.

What runs on this site. Store consoles and the submission service are external, so commands and config are read-only. The runnable stand-in is a pre-submission checklist written in plain JavaScript that checks an app.json-style object for common release mistakes.

What you need first

iOS Android
Account Apple Developer Program (paid, yearly) Google Play Console (one-time fee)
App record Created in App Store Connect Created in Play Console
Identifier Bundle identifier, set once Package name, set once
Binary .ipa from EAS Build (store distribution) .aab from EAS Build (store distribution)
Testing TestFlight Internal / closed / open testing tracks

On Google Play, the first upload of a new app must be done manually in the console. After that, eas submit can automate later uploads using a Google service account key.

Listing assets and information

Both stores need more than a binary. Prepare them early:

  • Name, subtitle/short description, full description, keywords (iOS) and a category.
  • Icon: 1024 x 1024 px PNG, no transparency on iOS, no rounded corners (the OS rounds them).
  • Screenshots for required device sizes (iPhone 6.9" and 6.5", iPad if you support it; phone and tablet shots on Android). Show real screens, not marketing mock-ups with fake features.
  • Privacy policy URL, required if you collect any data, and a support URL.
  • Privacy questionnaire: App Privacy "nutrition labels" in App Store Connect; the Data safety form in Play Console. They must match what your app and its SDKs do.
  • Age rating, and a test account (username and password) if the app needs login, so reviewers can get in.

Build for the store

Terminal
eas build --platform all --profile production

Make sure the production profile uses autoIncrement (EAS Build profiles), and the version in app config is the one you want users to see.

Submit with EAS

Terminal
eas submit --platform ios --latest
eas submit --platform android --latest
# or build and submit in one go
eas build --platform all --profile production --auto-submit

--latest picks your most recent build. EAS will ask for (and then remember) credentials:

  • iOS: your Apple ID and an App Store Connect API key, which is better than your password and works in CI. Create the key in App Store Connect under Users and Access, then pass it with eas credentials.
  • Android: a Google service account JSON key with permission to release for your app. Create it in Google Cloud and invite it in Play Console. Never commit this file.

Configure details in eas.json:

JSON
{
  "submit": {
    "production": {
      "ios": { "ascAppId": "1234567890", "appleTeamId": "ABCDE12345" },
      "android": {
        "serviceAccountKeyPath": "./play-key.json",
        "track": "internal",
        "releaseStatus": "draft"
      }
    }
  }
}

Start with track: "internal" and releaseStatus: "draft": the upload happens, but nothing reaches users until you press the button in the console.

Test tracks

flowchart LR
  A["Upload build"] --> B["TestFlight / Internal testing"]
  B --> C["External or closed testing"]
  C --> D["Store review"]
  D --> E["Staged rollout 5% to 100%"]

Move up a level only after the one below is stable.

  • TestFlight (iOS) lets up to 100 internal testers use a build almost immediately and up to 10,000 external testers after a light review. Builds expire after 90 days.
  • Play testing tracks: internal (up to 100 testers, instant), closed (invited groups) and open. New personal developer accounts must run a closed test with a minimum number of testers for a minimum number of days before production access, so start that early.

Review and common rejections

Apple reviews every version, typically within a day or two. Google reviews too, with new apps taking longer. The usual problems:

  1. Crashes or broken login. Test the exact production build on a clean device.
  2. Missing demo account for reviewers.
  3. Permission strings that are vague. NSCameraUsageDescription must say why: "Used to scan your receipts", not "Camera needed".
  4. Privacy mismatch. Declaring "no data collected" while including an analytics SDK.
  5. Placeholder content, "coming soon" screens, or an app that is just a website wrapper.
  6. No account deletion. Apple requires an in-app way to delete the account if you offer sign-up.
  7. Payments. Digital goods and subscriptions generally must use the store's in-app purchase system.

Write permission texts in app.json:

JSON
{
  "expo": {
    "ios": {
      "infoPlist": {
        "NSCameraUsageDescription": "Used to scan receipts so you can track expenses."
      }
    }
  }
}

Rollouts

On Google Play, release to a percentage of users first (for example 5%, then 20%, then 100%) and watch crash rates in the console. On iOS, use phased release over seven days. Pair this with over-the-air updates (next lesson): a store release carries native changes, while JavaScript fixes can follow quickly through EAS Update.

A pre-submission checker

Node.js Release checklist as code

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

The checker flags the example identifier, the one-word camera message and the empty privacy URL. Real stores check far more, but writing your own checklist as code catches the dull mistakes before a reviewer does.

Versions after launch

Increase version for visible releases (1.2.0 to 1.3.0); build numbers rise automatically. Keep a changelog, because both stores ask for "What's new" text. A native change (new permission, new native library) always needs a new store build; a JavaScript-only fix may not.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which file does Google Play require for new apps?

    Play requires app bundles for new apps. EAS store builds produce them.
  2. 2. What does eas submit --platform ios --latest do?

    submit uploads an existing build; it does not compile anything.
  3. 3. Why use releaseStatus draft with a track?

    Draft lets you inspect the upload in the console before publishing.
  4. 4. Which is a frequent cause of rejection?

    Reviewers need working access and honest explanations of permissions.

Summary

  • Prepare store accounts, listing text, screenshots, privacy forms and a demo account early.
  • Build with the production profile, then eas submit (or --auto-submit).
  • Use TestFlight and Play test tracks before public release, and roll out gradually.
  • Write specific permission texts and keep privacy declarations accurate.
  • Native changes need a store release; JavaScript fixes can use over-the-air updates.

Next: Over-the-air updates with EAS Update