How to Publish an Expo App to the App Store

Building a working iPhone app and publishing it on the App Store are different jobs. Expo simplifies the binary and submission workflow, but you still need to complete Apple's product, privacy and review requirements.

1. Prepare the iOS identity

Your application needs a stable iOS bundle identifier. Treat it as a permanent product identifier rather than a temporary development string.

You also need access to the Apple Developer Program and an App Store Connect app record.

2. Configure EAS

Install and sign in to the EAS CLI, then configure the project for builds if you have not already done so.

A production build commonly looks like:

eas build --platform ios --profile production

EAS can manage much of the signing workflow, but you remain responsible for the Apple account and app configuration.

3. Create the App Store Connect listing

Before review, prepare the information Apple requires, including the app name, description, screenshots, category, privacy information and other metadata relevant to your product.

Do this before the final day. Missing privacy details and screenshots can delay a release even when the binary is technically ready.

4. Submit the binary

EAS Submit can upload an iOS production build to App Store Connect:

eas submit --platform ios

Uploading a build does not automatically make the app public. The build becomes available in App Store Connect/TestFlight and still needs the appropriate release and review steps.

5. Test with TestFlight

Use TestFlight to verify the production-style build. Test real authentication, purchases, deep links, notifications and any feature that behaves differently outside development.

A final TestFlight pass is also a good place to verify that analytics and error tracking are working.

6. Submit for App Review

In App Store Connect, associate the correct build with the version, complete required metadata, add the version for review and submit it.

If the app requires an account, provide review access or clear instructions where Apple requests them.

7. Treat rejection as product feedback, not just paperwork

App Review can surface issues in privacy disclosures, login flows, payment rules, broken links, incomplete functionality or reviewer access.

Fix the underlying issue and keep the review notes concise and factual.

8. Prepare for the financial side of launch

After the first paid download, subscription or in-app purchase, App Store Connect becomes more than a release dashboard. Sales, proceeds and payouts are different financial concepts.

Build a monthly process for reading platform reports instead of relying on one dashboard number or one bank deposit.

The complete shipping loop

A sustainable mobile workflow is:

build → TestFlight → review → release → measure → monetize → reconcile.

Publishing is the midpoint between coding and operating a real app business.