Deploy Expo Apps to Production

This skill guides an agent through deploying Expo applications with EAS (Expo Application Services) across every target platform. It covers building and submitting iOS and Android releases, configuring build and submit profiles in eas.json, managing app versions and build numbers, publishing App Store metadata and ASO, and deploying web bundles and API routes through EAS Hosting.

The skill is organized around a Quick Start (installing the EAS CLI, logging in and initializing a project), a set of build and submit commands, a web deployment section, a reference eas.json, platform-specific guides for iOS, Android and Web, automated deployments, version management and monitoring. It also points to five reference files for deeper topics: CI/CD workflows and PR previews, TestFlight submissions, App Store metadata and ASO, Google Play Store submission, and the iOS App Store review process.

Initialization creates an eas.json containing build profiles. Production builds are started per platform or for both at once with a profile flag, and adding the submit option sends the finished build to App Store Connect or the Play Store. A shortcut command, npx testflight, handles quick iOS TestFlight submissions.

npx eas-cli@latest build -p ios --profile production

Use it when you need to ship an Expo app to production with EAS: building and submitting to the iOS App Store, Google Play Store and TestFlight, configuring build and submit profiles, managing versions and build numbers, publishing store metadata, or deploying web bundles and API routes.

Do not use it for authoring the API routes themselves; the skill sends you to the separate expo-api-routes skill for that, since eas deploy ships the routes together with the web bundle. Likewise, for writing or validating workflow YAML it defers to the expo-cicd-workflows skill, which works from the live workflow schema. The skill's own Limitations section adds three cautions: apply it only when the task clearly matches its upstream product scope, verify commands, pricing, quotas, credentials and deployment effects against current official documentation before changing anything, and never treat generated examples as a substitute for environment-specific tests, security review or user approval for destructive or costly actions.

Inputs are an Expo project, an EAS login and the credentials each store needs. For iOS that means an Apple ID and an App Store Connect app ID in the submit profile, with credentials configured through eas credentials. For Android it means a Google Play Console service account key file and a release track, and the guide lists the track progression as internal, closed, open, production.

Outputs are store builds and submissions, version numbers managed remotely when appVersionSource is set to remote, and web deployments. Production web deploys go out with an export followed by a deploy command with the prod flag, while a plain deploy produces a PR preview. Expo Router API routes ship together with the web bundle on EAS Hosting.

For monitoring, the skill lists commands to view recent builds, check the status of a build and see submission status. For versions, it shows how to read the current values and how to set an iOS build number by hand.

The skill also works with EAS Workflows, and EAS Hosting provides preview URLs for pull requests. The published web app can run on your custom domain.

Mobile and full-stack developers who build with Expo and want a repeatable path from a working app to store releases, including teams that want CI/CD automation of the build, submit, update and deploy pipeline. It is published under the MIT license and marked with a critical risk level in its metadata, which is a reminder that deployments have real effects and should be reviewed before running.