This is the last stretch: the app is built, and you want it in TestFlight and then on the App Store. One step is done from the discussion. The rest happens in App Store Connect, Apple's own site, because Apple wants the account's owner to make those choices.
Before you send
- Create the app in App Store Connect. Under My Apps, press the plus button, choose New App, and pick the same bundle identifier the room put in the project. Give it a name (it must be unused on the store) and a primary language.
- Find its Apple ID. Under App Information, in General Information, is a number called Apple ID. The room asks you for it once and writes it in the project.
- Have a store build. In the Try on Phone panel, under Build, ask for For TestFlight and the App Store and wait until it says Ready.
Send it
Where to find it. In the discussion, Try on Phone, Build: a finished store build has Send to App Store Connect.
What happens. The button puts a request in the message box; send it. A card asks you first. On yes, your Cloud Computer uploads the build with your App Store Connect key. The build then shows Sent to App Store Connect in the panel.
Apple processes an upload for about 10 to 15 minutes. After that it is under TestFlight in App Store Connect.
What it does not do. It submits nothing for App Review and publishes nothing. That press is yours.
If Apple says a build with that version and number is already there, ask for a new store build; its number goes up by itself.
Test with TestFlight
Install the TestFlight app on your iPhone and sign in with the Apple account on your membership: the build is there to install. The first time, App Store Connect asks whether the app uses encryption beyond what iOS provides; most apps answer no. Ask the room to set that in the project's app.json so the question stops coming.
Add people on your team as internal testers at once. Testers outside it, by address or by a public link, need a short Beta App Review of the first build.
The listing
Under the app's App Store tab, a version cannot be submitted until these are filled in:
| What | Notes |
|---|---|
| Screenshots | For the iPhone sizes App Store Connect lists. Take them on a real phone in TestFlight |
| Description, keywords, support address | The room can draft the words; you paste them |
| Privacy policy address | Required for every app |
| App Privacy | What data the app collects and why, answered as a questionnaire |
| Age rating | A questionnaire |
| Category, copyright, contact for the reviewer | A sign-in for the reviewer if the app has accounts |
Then choose the build you sent, and press Add for Review and Submit for Review.
App Review
Apple reviews most submissions within a day or two. A rejection comes with the guideline it failed and a place to reply. The common ones for a first app: it crashed or a button did nothing; it had placeholder text; it asked for a sign-in the reviewer was not given; it was a thin wrapper around a website; or it sold digital content without in-app purchase. Fix it with the room, build, send and submit again.
You choose whether an approved version goes out at once or when you release it.
Price, and selling it
Under Pricing and Availability choose Free or a price, and the countries. To charge anything, first accept the Paid Apps agreement under Business and enter your tax and bank details; Apple pays you monthly, after its commission, which is lower for small sellers who enrol in its small business programme.
In-app purchases and subscriptions
Anything digital sold inside the app, such as a pro tier, credits or a subscription, has to go through Apple's in-app purchase. Three parts:
- In App Store Connect, create each product or subscription group, with its price and a screenshot for review. The first ones are reviewed together with an app version.
- In the app, ask the room to add purchases with a purchases library for Expo, a restore-purchases button, and a check of what the person owns. This needs a real build; it does not work inside Expo Go.
- Test with a sandbox tester account from App Store Connect, in a TestFlight build, where purchases cost nothing.
Physical goods and services used outside the app are different: they use an ordinary payment provider, not in-app purchase.
When not to use this page. For an app written in Swift on a Mac: Xcode uploads it, and the App Store Connect steps are the same from "Test with TestFlight" on.