Skip to content

Free submission guide · Verto Studios · Updated

App Store Submission Checklist for Expo Apps

Before submitting an Expo iOS app, verify the exact release build, saved App Store Connect metadata, purchase configuration and reviewer access. Keep evidence for each check. A successful upload alone does not establish that these steps are complete.

This is a compact checklist for standard iOS submissions. Apple makes the review decision; specialized app categories may need additional checks.

1. Match the app and the release record

Compare the bundle identifier in your Expo configuration, Apple app record and intended binary. Write down the version and build you will test. Reusing a checklist from a different build can hide a mismatch.

Keep as evidence: One release record identifying the exact artifact and store version.

2. Test the production build on a device

Cold launch the intended release build. Exercise sign-in, the main task, failure states and any permission prompts. Development mode and Expo Go are useful during development; they do not establish how the submitted artifact behaves.

Keep as evidence: Device, build, test steps and observed results; unresolved failures have an owner.

3. Check the saved store metadata

Open the intended App Store Connect version and check the selected build, description, screenshots, support link and required declarations. Open public URLs without your signed-in browser session. Read the saved values after editing.

Keep as evidence: The saved version record and working destinations, with identifying details kept private.

4. Trace subscriptions across all systems

If the app sells subscriptions, compare each product ID in the app, purchase provider and App Store Connect. Verify the offering and entitlement, complete a test purchase and test restoration. Separately check that the first products are included with the review submission.

Keep as evidence: Product map, saved review selection and transaction-to-entitlement test results.

5. Test privacy and account controls

Check that permission explanations describe the actual feature. Open Terms and Privacy links from the subscription screen when applicable. If accounts can be created, test the deletion path and its backend effect; signing out is not account deletion.

Keep as evidence: Observed permission, link and deletion behavior from the release build.

6. Rehearse the reviewer's path

Start from a clean install and follow your own review notes. Confirm that the reviewer can reach the relevant features with the access you provide. Check backend availability, demo data and any account restrictions. Keep credentials in the private review fields.

Keep as evidence: Short, reproducible review instructions tested against the submitted build.

EAS Submit iOS: does uploading send the app to App Review?

EAS Submit uploads an iOS build to App Store Connect, where it becomes available through TestFlight after processing. You still complete the store submission and send it for App Review. Before uploading, answer the Expo export compliance and App Store encryption questions. See Expo’s iOS submission documentation and Apple’s review submission overview.

What can a coding agent verify?

An agent can inspect the repository evidence you give it, such as app identifiers, dependency versions and configured permission text. Store selection, reviewer access and device behavior need separate evidence. An honest report leaves missing evidence unresolved.

Work through a specific issue

If Apple rejects the app anyway

Look the message up in the free App Store rejection fixes by guideline: one page per rejection, with Apple's words, what they mean and what to check first, from Guideline 2.1(a), app did not load to Guideline 2.1(b), purchases not submitted.

SubmitPreflight: After Rejection is a PDF guide, in phone and desktop editions, with 18 fix pages. Each gives Apple's words, what to check, the App Store Connect clicks, a prompt for your AI app builder and a reply to Apple. It also covers Apple's current purchase flow and a final check before you resubmit. The price is $19 USD one-time. It is available from the product page.

See the guide · Read 16 free PDF pages · Free rejection checklist (PDF)

Official references

Use current official instructions when requirements change. This checklist is an editorial workflow, not an Apple certification.