GuidesMobile apps

Tutorial: publishing an Expo app to the App Store and Google Play with EAS

By the Banzai Labs teamUpdated on 3 min read

eas build · eas submitCloud buildApp StoreGoogle PlayOne command builds, another submits to the stores
EAS builds the app in the cloud, then submits it to the App Store and Google Play.

1. Prerequisites

  • An Apple Developer Program account and a Google Play Console account.
  • An Expo account, and the command-line tool:
npm install -g eas-cli
eas login
eas build:configure

2. Build

eas build --platform all --profile production

EAS handles the iOS certificates and the Android signing key, unless you provide your own.

3. Submit to the stores

eas submit --platform ios
eas submit --platform android

On Google Play, the very first release of an app usually has to be uploaded by hand from the console; later ones go through eas submit.

4. The release path

  1. 1Version numberBumped in app.json, or automatically by EAS.
  2. 2Production buildIn Expo's cloud.
  3. 3Internal testingTestFlight and Google Play internal testing.
  4. 4ReleaseStore listing, screenshots, then submit for review.

5. Quick fixes

eas update --branch production --message "Fix the cart"

Users get the new JavaScript on the next launch, without going through the stores.

For the starting choice: Expo or native development. The full path: building a mobile app.

Frequently asked questions

Do I need a Mac to publish on the App Store?
Not with EAS: the iOS build runs on Expo's servers. You do need a paid Apple Developer Program account.
How long does review take?
It depends on Apple and Google and varies over the year. Leave some margin before a launch date.
What can I fix without going through the stores?
JavaScript code and images, with EAS Update. A change to native code or permissions needs a new store release.

Projects where we did it

Read next

All guides