This documentation is available as Markdown for AI agents and LLMs. See the full Markdown index or append .md to any documentation URL.

Submit to app stores

Edit page

An overview of how to submit your app to the Google Play Store and Apple App Store.


Releasing an app means uploading a signed binary (.aab for Android, .ipa for iOS) to Google Play Console or App Store Connect. From there, Google and Apple manage review, testing tracks, and production rollout.

You have two options for getting a binary into each store: submit with Expo Submit, or upload manually through the store's own tools. Expo Submit is the recommended path since it works from any OS (including Windows and Linux for iOS), integrates with Expo Build and Expo Workflows, and can be run from a CI/CD service. Manual uploads are useful when you aren't using Expo Services, or when you prefer to create your Android app's first release directly in Play Console.

How to quickly publish to the App Store & Play Store with Expo Submit
How to quickly publish to the App Store & Play Store with Expo Submit

Expo Submit makes it easy to publish your apps to the App Store and Play Store with a simple command.

How Expo Submit works

A submission is one upload of a build to Google Play Console or App Store Connect. eas submit creates one submission for each platform that you choose. You can see your submissions on the Submissions page of your project in the Expo dashboard.

Android (Google Play Store)

Before the first submission, create the app in Google Play Console. Expo Submit uploads your .aab to Google Play Console and places it in the track you choose (internal, alpha, beta, or production). For a brand-new app, the default eas submit command creates the first release on the internal testing track, even before you complete the store listing. To distribute beyond internal testing, finish the setup tasks in Play Console and promote the release. To upload a build without rolling it out to its track, set releaseStatus to draft in eas.json.

iOS (Apple App Store)

If your app is not in App Store Connect yet, eas submit creates it after you sign in with your Apple ID. Expo Submit uploads your .ipa to App Store Connect, where it becomes available in TestFlight after processing (usually 10-15 minutes). A TestFlight build is not automatically released to the App Store. To ship it to production, sign in to App Store Connect, complete the app metadata and screenshots, select the build, and submit it for App Review.

When to use Expo Submit

ScenarioRecommendation
Upload app binaries to Google Play Console and Apple App Store
Upload iOS app binaries from Windows or Linux
Avoid manual uploads through Play Console, App Store Connect, or Transporter
Submit builds from CI or automated workflows
Standardize release processes via eas.json config
Testing during development

Choose a submission path

Submit to the Google Play Store with Expo Submit

Recommended. Upload your Android build to Google Play Console with a single command, from your computer or CI.

Submit to the Apple App Store with Expo Submit

Recommended. Upload your iOS build to App Store Connect and TestFlight from any OS, including Windows and Linux.

Manually submit an Android app for the first time

Follow a step-by-step Play Console walkthrough to create your Android app's first release.

Manually submit an iOS app with Xcode

Build, archive, and upload an iOS app to App Store Connect using Xcode on macOS.

Expo Skills for AI agents

If you use an AI agent, install Expo Skills to teach it how to submit and release your app:

eas-app-stores

Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play.

Frequently asked questions

Can I submit a new build before the previous one is released?

Yes. Create a new build. Then run eas submit again. Each upload needs a new android.versionCode or ios.buildNumber, because the stores reject a build that reuses one. To increment these values on every build, use the remote version source with autoIncrement.

  • On Android, Expo Submit uploads the new build to the track that you choose.
  • On iOS, the new build appears in App Store Connect after processing. Select it for your App Store version before you submit the version for App Review. If you already submitted the version, remove it from review before you select the new build.
Can I submit builds that were not built with Expo Build?

Yes. Expo Submit accepts any valid .aab (Android App Bundle) or .ipa (iOS App Archive) file.

For builds created with Expo Build, run eas submit and select a build from the list or let it use the latest build automatically.

For local builds, use the --path flag to specify the binary:

Terminal
- eas submit --platform android --path ./my-app.aab

- eas submit --platform ios --path ./my-app.ipa

The binary must be correctly signed. For Android, this means an upload keystore. For iOS, this means a distribution certificate and provisioning profile.

Does Expo Submit handle store metadata or screenshots?

Expo Submit uploads your binary but does not manage store listing metadata, screenshots, or release notes.

For Google Play Store, configure your store listing directly in Google Play Console before submitting.

For Apple App Store, you can use Expo Metadata to automate app information and localized descriptions.

How do I know why my submission failed?

Open the submission details page in the Expo dashboard:

  • Read the logs on the submission details page to understand the error.
  • Look for a "Build Annotations" bubble — these highlight common failure reasons and suggested fixes directly in the logs.
Can I use Expo Submit inside Expo Workflows or from other CI/CD pipelines?

Yes. Expo Submit works in CI environments and integrates with Expo Workflows. You can add a submit job to your workflow configuration. For example:

jobs: submit_ios_to_store: type: submit needs: [build_ios] params: build_id: ${{ needs.build_ios.outputs.build_id }}

For more information, see Expo Workflows pre-packaged jobs.

For CI pipelines, you can also use the --non-interactive flag to skip prompts and --latest to automatically select the most recent build:

Terminal
- eas submit --platform android --latest --non-interactive

With --non-interactive, Expo Submit cannot prompt you for a Google Service Account key or an App Store Connect API Key. Set up the key for your app first, as described in Submit to Google Play Store and Submit to Apple App Store.