How to publish an iOS app to the App Store, step by step (2026)

Set up your account and the app record

Before you can submit anything, you need an account and a place for the app to live.

1. Join the Apple Developer Program. This is a paid annual membership and is required to distribute on the App Store. Set up your team and accept the agreements.
2. Reserve a Bundle ID. Register a unique Bundle ID for the app in your developer account.
3. Create the app in App Store Connect. Add the app with its name, primary language, Bundle ID, and the category that fits it.

Build, sign, and beta test

Next you produce the actual binary and put it in front of testers.

1. Build for distribution. Compile a release build of your native iOS app with a current Xcode toolchain.
2. Code sign it. Sign the build with a distribution certificate and provisioning profile so Apple accepts it.
3. Upload to App Store Connect. Upload the build from Xcode, the command line, or the App Store Connect API. You do not have to drive this from Xcode; see the guide on submitting without Xcode.
4. Test on TestFlight. Once the build processes, test it through TestFlight with internal testers, and with external testers after the first build clears beta review. Fix what you find before submitting for sale.

Prepare metadata and submit for review

A working build is not enough. The store listing has to be complete and accurate.

1. Add screenshots. Provide screenshots at the current required sizes, the 6.9-inch iPhone set and, if you support iPad, the 13-inch iPad set. Show the app in use, not just a splash screen.
2. Write the listing. Add the description, keywords, support URL, and a working privacy policy URL. Keep everything accurate to what the app does, which is what Guideline 2.3 requires.
3. Set the age rating and pricing. Answer the age rating questions honestly and set price and availability.
4. Attach the build and add review notes. Select the processed build, and in the App Review information add a demo account if the app has a login, with your back-end running, plus notes describing new features.
5. Submit for review. Submit the version for App Review.

Apple then reviews the app against its guidelines. Review time varies and is not a fixed turnaround, so do not promise a launch date you cannot control.

Handle the outcome and release

After review, one of two things happens.

• Approved. You can release the app immediately, schedule a release date, or release it manually, then monitor for crashes and reviews.
• Rejected. Apple cites the guideline the app failed. You fix the underlying issue in the build or the metadata and resubmit, or respond in the resolution center if you need clarification. Each resubmission is reviewed again.

Because submitted is not approved, the work does not end at submission. Plan for the chance of a rejection and a fix cycle.

How AppFlight runs this for you

AppFlight turns a plain-English prompt into a native iOS app in Swift and SwiftUI, then runs this whole sequence in one app: it builds, runs a live simulator, passes an automated test gate, handles code signing, uploads to TestFlight, sets metadata, and submits for full App Store review. Its marketing autopilot helps with the icon, screenshots, and ASO. If Apple rejects a build, AppFlight reads the rejection reason, works on the fix, and resubmits. You bring your own AI, Claude Code or Codex, running locally on your Mac, and you still need an Apple Developer account and accurate metadata. AppFlight does not guarantee approval. Apple reviews every app, and submitted is not the same as approved.