# Shipping an Expo app to the App Store

> What AI app builders don't handle when you go to the App Store: Apple accounts, EAS builds, in-app purchase rules, review guidelines and common rejections.

By Tommy Pham · 2026-11-14 · https://tommydev.web.app/blog/expo-app-store-submission

**Short answer:** an AI builder can give you a working React Native or Expo app, but getting it into the App Store means an Apple Developer account, a signed build (EAS Build makes this manageable), a complete App Store Connect listing, and an app that passes review. The rejections that catch AI-built apps most often are **4.2 minimum functionality** (it's basically a website), **3.1.1 in-app purchase** (selling digital goods without Apple's billing), missing **account deletion**, and incomplete **privacy details**.

I was the lead developer on [Pocket Party](/work/pocket-party), a React Native + Expo app for iOS and Android with in-app purchases.

Part of my [launch guide](/blog/launch-vibe-coded-app).

## What do you need before you start?

- **An Apple Developer Program membership** ($99 a year). Enroll as an organization if you have a company, which also shows the company name on the store.
- **A Mac isn't required** with EAS Build, which builds in the cloud. You'll still want a real iPhone for testing.
- **A privacy policy URL** and a **support URL**.
- **App Store screenshots** for the required iPhone sizes (and iPad, if you support it).

## How do you build and submit with Expo?

Expo's EAS handles certificates and provisioning profiles, the part that used to take a day:

```bash
npm i -g eas-cli
eas login
eas build:configure
eas build --platform ios --profile production
eas submit --platform ios
```

`eas submit` uploads the build to App Store Connect. From there, test it with **TestFlight**, then submit for review. Set up `eas update` for over-the-air JavaScript updates, but remember that Apple's rules still apply to anything you change that way.

## Which review guidelines catch AI-built apps?

| Guideline | What triggers it | How to avoid it |
|---|---|---|
| **4.2 Minimum functionality** | The app is a thin wrapper around a website, or has very little to do | Real native screens and a clear core feature that works well in-app |
| **3.1.1 In-app purchase** | Digital content, features or subscriptions sold through Stripe or a web checkout | Use StoreKit (via RevenueCat or `react-native-iap`) for digital goods. Some storefronts, such as the US, now allow linking out to web checkout, so check current rules |
| **5.1.1(v) Account deletion** | Users can create an account but can't delete it in the app | Add a delete-account option that actually deletes the data |
| **2.1 App completeness** | Crashes, placeholder text, broken links, a demo login that doesn't work | Test the release build. Give the reviewer working demo credentials |
| **5.1.1 Privacy** | Privacy labels don't match what the app collects. Missing tracking permission prompt | Fill in App Privacy honestly. Show ATT if you track across apps |
| **4.8 Login services** | Third-party social login without an equivalent privacy-focused option | Also offer a login that limits data to name and email, such as Sign in with Apple |

Read Apple's current [App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/) before submitting. They change, and reviewers apply them strictly.

## How do in-app purchases work in practice?

- Create products (consumables, non-consumables or subscriptions) in App Store Connect.
- Use a library that wraps StoreKit and Google Play Billing. **RevenueCat** is the common choice because it also handles receipts and subscription status across platforms.
- **Unlock content from verified purchase state**, never from a client-side flag.
- Offer **Restore Purchases**, which reviewers check for.
- Test with sandbox accounts and TestFlight before review.

Pocket Party's premium game packs used in-app purchases on iOS and Android.

## What about Android?

Google Play has its own path: Play Console, `eas submit --platform android`, the data safety form, and, for new personal accounts, a 12-tester closed test. If you already have a good PWA, a TWA can get you onto Google Play without a native rebuild. → [TWA guide](/blog/pwa-to-google-play-twa)

## FAQ

### How long does App Store review take?

Often a day or two, sometimes longer, especially for first submissions or after a rejection. Leave buffer before any launch date.

### Can I ship a web wrapper to the App Store?

It's risky. Apple rejects apps that only display a website under guideline 4.2. Add genuine native functionality, or build the app in React Native or Expo.

### Can I use Stripe in my iOS app?

For physical goods and real-world services, yes. For digital goods and subscriptions used in the app, Apple generally requires in-app purchase. Rules vary by region and app type, so check the current guidelines for your case.

### Do I need RevenueCat?

No, but it saves writing receipt validation and cross-platform subscription logic yourself.

---

Getting an app through the stores is a big part of what I've done. If you're stuck on builds, purchases or a rejection, see [my work](/#work) or get in touch below.

## Sources

- Apple: [App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/) and [Apple Developer Program](https://developer.apple.com/programs/)
- Expo docs: [EAS Build](https://docs.expo.dev/build/introduction/) and [EAS Submit](https://docs.expo.dev/submit/introduction/)
- RevenueCat: [The ultimate guide to App Store rejections](https://www.revenuecat.com/blog/growth/the-ultimate-guide-to-app-store-rejections)
- Checked November 2026