Publish an Expo App to Google Play & App Store in 2026
Building the app is the fun part. Getting it into Google Play and the App Store is where a lot of first-time developers get stuck, usually not on code but on accounts, forms and rules nobody told them about.
This guide walks through the whole route for an Expo (React Native) app as things stand in November 2026: what to set up before you build, the exact commands, the store rules that changed this year, and the small mistakes that cost people a week. If you have never shipped an app before, you can follow it top to bottom.
Last checked: November 9, 2026. Store rules change every year, so links to the official pages are at the end.
The short version
| Step | Google Play | App Store |
|---|---|---|
| Developer account | $25 one-time | $99 per year |
| What you upload | .aab (Android App Bundle) |
.ipa |
| Build requirement | Target Android 16 (API level 36) | Built with Xcode 26 and the iOS 26 SDK or later |
| Testing before launch | New personal accounts: 12 testers for 14 days | TestFlight is optional |
| Review time | Usually hours to a few days | Usually a day or two |
| Command | eas submit --platform android |
eas submit --platform ios |
If you use a current Expo SDK and build with EAS, the build requirements are mostly handled for you. The paperwork is not, and that is what the rest of this post is about.
Before you build anything
Sort these out first. Each one can block you later, and some take days.
1. Create both developer accounts early. Google Play asks for identity verification, and an organization account needs a D-U-N-S number, which can take a while to get. Apple enrollment can also take a few days. Start these on day one, not on launch day.
2. Decide your app's ID and never change it. This is the unique name stores use for your app, written like a reversed domain:
{
"expo": {
"name": "Daily Brief",
"slug": "daily-brief",
"version": "1.0.0",
"ios": { "bundleIdentifier": "com.yourcompany.dailybrief" },
"android": { "package": "com.yourcompany.dailybrief" }
}
}
Once an app is published with an ID, you cannot rename it. A typo here means a brand-new store listing with zero reviews.
3. Prepare a privacy policy URL. Both stores require one, even for simple apps. It must be a real public web page, not a PDF in Google Drive.
4. Plan account deletion if users can sign up. If your app lets people create an account, both stores expect a way to delete it. Apple wants the option inside the app. Google asks for a deletion link in the Data safety form. Building this at the end is painful, so put it on your list now.
5. Get your store assets ready. You will need an app icon (1024 × 1024 for Apple, 512 × 512 for Google), screenshots for phones, a short description, a full description and a feature graphic for Google Play (1024 × 500).
Set up EAS once
EAS (Expo Application Services) builds your app in the cloud and uploads it to the stores. You don't need a Mac to build for iOS.
npm install --global eas-cli
eas login
eas build:configure
The last command creates an eas.json file. A simple setup that works for most apps looks like this:
{
"cli": { "appVersionSource": "remote" },
"build": {
"preview": { "distribution": "internal" },
"production": { "autoIncrement": true }
},
"submit": {
"production": {}
}
}
autoIncrement with appVersionSource: remote means EAS bumps the build number for you on every production build. Forgetting to bump it is one of the most common upload errors ("version code has already been used"), and this setting removes that problem completely.
Publishing to Google Play
Step 1: Build the Android App Bundle
eas build --platform android --profile production
Google Play only accepts .aab files for new apps. EAS creates one and manages your upload key, so there is no keystore file for you to lose.
The 2026 rule to know: since August 31, 2026, new apps and updates must target Android 16 (API level 36) or higher. A recent Expo SDK already does this. If your project is on an old SDK, upgrade first, or Play Console will reject the upload.
Step 2: Create the app in Play Console
In Play Console, choose Create app, enter the name and language, and mark it as an app or game, free or paid. Be careful with free: a free app cannot later become paid.
Then work through the Set up your app checklist on the dashboard. It includes:
- Privacy policy: your URL from earlier.
- App access: if parts of your app need a login, give reviewers a test account. Missing login details is a very common rejection reason.
- Ads: say whether the app shows ads.
- Content rating: a questionnaire that gives you age ratings for each region.
- Target audience: if you include children under 13, stricter rules apply.
- Data safety: what data you collect, why, and whether it is shared. Remember that this includes data collected by libraries such as analytics and crash reporting tools.
Step 3: Upload with EAS Submit
EAS needs a Google service account key (a JSON file) to upload on your behalf. Expo's guide at expo.fyi/creating-google-service-account walks you through creating one in about ten minutes. Then:
eas credentials --platform android
eas submit --platform android
By default, the first submission goes to the internal testing track. That is a safe place: only people you invite can install it.
Step 4: The 12 testers rule (personal accounts)
This is the step that surprises the most people. If you have a personal developer account created after November 13, 2023, Google will not let you publish to production straight away. You must first run a closed test with at least 12 testers who stay opted in for 14 days in a row.
A few practical tips:
- Recruit more than 12, say 15 to 20. If someone opts out, you don't want the count to drop below 12.
- The 14 days have to be continuous for each tester. Someone who leaves and joins again starts over.
- Ask testers to actually use the app. When you apply for production access, Google asks how testing went, what feedback you got and what you changed.
- Organization accounts are exempt from this rule.
So when you plan a launch date on a personal account, add at least two weeks for this.
Step 5: Apply for production and roll out
After 14 days, Play Console shows an Apply for production button. Answer the questions honestly and in your own words. Once approved, create a production release, and consider a staged rollout (for example 20% of users first) so a bad bug doesn't reach everyone at once.
One more 2026 change: Android developer verification. From September 30, 2026, apps in Brazil, Indonesia, Singapore and Thailand must come from verified developers, and Google says this expands worldwide in 2027. Most Play developers are already verified, but check the Play Console home page for a notice and register any app it lists.
Publishing to the App Store
Step 1: Create the app record in App Store Connect
In App Store Connect, go to Apps, click + and choose New App. Pick the same bundle identifier you set in app.json. Once the record exists, copy its Apple ID (a number) from App Information. EAS uses it to know where to upload.
Step 2: Build and submit
eas build --platform ios --profile production
eas submit --platform ios
Or do both in one command:
eas build --platform ios --auto-submit
On the first run, EAS asks you to log in with your Apple ID and offers to create the certificates and provisioning profile for you. Let it. Managing iOS certificates by hand is where many beginners lose a whole afternoon.
The 2026 rule to know: since April 28, 2026, every upload to App Store Connect must be built with Xcode 26 or later using the iOS 26 SDK. EAS Build uses current Xcode images for recent Expo SDKs, so this is handled if you keep your SDK up to date.
Step 3: Test with TestFlight
After processing (usually 10 to 15 minutes), the build appears in TestFlight. Install it on a real iPhone and go through the main flows once: sign up, log in, the main screen, payments if you have them. Testing the release build matters because some issues only show up there, never in development.
Step 4: Fill in the listing and submit for review
Add screenshots, a description, keywords, the support URL and your privacy policy. Then complete the App Privacy section (Apple's version of Data safety) and the age rating questions. Apple updated the age rating questionnaire this year, so answer it fresh even if you have published apps before.
Choose the build, click Add for Review, and submit.
Why apps get rejected, and how to avoid it
These are the reasons we see most often, on both stores:
- Reviewers can't log in. Always give a working demo account in the review notes, and make sure it doesn't expire or need a one-time code sent to your phone.
- The app looks unfinished. Placeholder text, "Lorem ipsum", empty screens or buttons that do nothing. If a feature isn't ready, hide it.
- The privacy answers don't match the app. If you use analytics or crash reporting, that is data collection, and the forms must say so.
- Permissions without a reason. On iOS, every permission (camera, location, photos) needs a clear message explaining why. In Expo you set these in
app.json. "This app needs your location" is too vague; "Used to show stores near you" is right. - The app is just a website. Apple rejects apps that only wrap a website without adding anything an app can do.
- Crashes on launch. Usually a missing environment variable or an API key that only exists on your computer. Test the production build, not just the development one.
After launch: updates
For later versions, the routine is short:
- Change
versioninapp.json(for example1.0.0to1.1.0). - Run
eas build --platform all --profile production. - Run
eas submitfor each platform, or use--auto-submit.
For small JavaScript-only fixes, EAS Update can push changes straight to users without a new store review. It can't change native code or permissions, and the change has to follow the store rules, so use it for fixes and small tweaks, not whole new features.
Frequently asked questions
Do I need a Mac to publish an iOS app with Expo? No. EAS Build compiles your iOS app in the cloud, and EAS Submit uploads it. You do still need a paid Apple Developer account, and an iPhone to test on is strongly recommended.
How long does the whole process take? Plan on about three weeks for a first Android launch on a personal account, mostly because of the 14-day closed test. A first iOS launch is often ready within a week, including review. Later updates usually go live within a day or two on both stores.
Can I publish an app that runs in Expo Go?
No. Expo Go is only a tool for development. Users install your own built app from the store, which is what eas build produces.
Which Expo SDK should I use? The newest stable one you can. Expo SDK 58 came out in October 2026, but the new Expo Go app for it rolls out a few weeks later. If your project uses a development build, you can upgrade right away. Newer SDKs keep you ahead of the yearly store requirements.
My upload was rejected for the target API level. What now?
Upgrade your Expo SDK (npx expo install expo@latest, then npx expo install --fix), rebuild and upload again. Upgrade one SDK version at a time if you are several behind, and read each version's upgrade notes, because skipping straight to the newest one makes problems harder to track down.
Wrapping up
Publishing an Expo app in 2026 comes down to three things: set your app ID and accounts up early, let EAS handle builds, signing and version numbers, and give each store the information it asks for, honestly and completely. The code is usually ready long before the paperwork is, so start the paperwork first.
If you are starting a new app and want a head start on the screens, our React Native and Expo UI kits come with clean, documented code you can take straight to eas build.
Sources
- Google Play: Target API level requirements
- Google Play: Testing requirements for new personal developer accounts
- Android: Android developer verification
- Apple: Upcoming requirements for App Store Connect
- Expo: Submit to the Google Play Store and Submit to the Apple App Store
- Expo: Expo SDK 58 release notes
Sources
The facts in this article were checked against these sources.
- Target API level requirements developer.android.com
- Testing requirements for new personal developer accounts support.google.com
- Android developer verification developer.android.com
- Upcoming requirements for App Store Connect developer.apple.com
- Submit to the Google Play Store docs.expo.dev
- Submit to the Apple App Store docs.expo.dev
- Expo SDK 58 release notes expo.dev