LimitedRound 2 is open. Get your first month free, no extra charge.Join the waitlist ›
From build to App Store

Complete guide to shipping an iOS app (2026)

TL;DR. Shipping an iOS app in 2026 has a fixed set of stages: a paid Apple Developer account, a signed build, an app record in App Store Connect, TestFlight testing, complete metadata, and a submission for App Review. Each stage has its own requirements, like a bundle ID, distribution signing, screenshots, a privacy policy, and an age rating. Apple reviews every app, so submitted is not approved. AppFlight runs the whole flow from prompt to submission.

Stage 1: account and identity

Before anything ships, two foundations have to exist:

  • A paid Apple Developer Program membership, which is 99 USD per year. This is required for any App Store distribution.
  • A bundle ID, the unique reverse-DNS identifier for the app, registered as an App ID. Pick it carefully, because it cannot be changed once an app record uses it.

These two carry through every later stage, since signing, the app record, and the store listing are all bound to them.

Stage 2: build and sign

Next the app has to become a real, signed binary:

  1. Build the app with a current Xcode and iOS SDK. Apple requires Xcode 14 or later for App Store uploads in 2026.
  2. Sign it for distribution with an Apple Distribution certificate and an App Store provisioning profile. The certificate proves who built it, and the provisioning profile ties that identity to the bundle ID and entitlements.
  3. Set the encryption declaration with the ITSAppUsesNonExemptEncryption key, which most apps can answer as exempt. See export compliance.
  4. Produce a distribution .ipa with an incrementing build number.

If signing is wrong, nothing uploads, so this stage is where many first attempts stall.

Stage 3: App Store Connect, TestFlight, and metadata

With a signed build in hand, the work moves to App Store Connect:

  • Create the app record bound to your bundle ID.
  • Upload the build and let it finish processing, then attach it to TestFlight. Test with internal testers first, then external testers if you want a wider beta.
  • Fill in the metadata: app name, subtitle, description, keywords, screenshots at the required sizes, a privacy policy URL, the App Privacy details, and the age rating questionnaire.

Incomplete or inconsistent metadata is one of the most common reasons a submission is delayed or rejected, so this stage rewards being thorough.

Stage 4: submit, review, and release

The last stage is the actual submission:

  1. Attach the processed build to your app version and submit for App Review.
  2. Wait for review. It is often completed within 24 hours, though it can take longer, and the first external TestFlight build of a version also needs a separate Beta App Review.
  3. If Apple rejects the build, read the specific guideline cited, fix the issue, and resubmit.
  4. Once approved, release immediately, on a schedule, or in a phased rollout.

Throughout, keep one fact in mind: submitting an app is not the same as it being approved. Apple reviews every app, and approval is Apple's decision.

Where AppFlight fits

AppFlight is a macOS app that turns a plain-English prompt into a native iOS app in Swift and SwiftUI, then runs this entire journey in one place. It builds the app, runs it in a live iOS simulator, puts it through an automated test gate, signs it for distribution, uploads to TestFlight and App Store Connect, sets metadata, and submits for full review. If Apple rejects the build, it reads the reason, works on the fix, and resubmits. You bring a paid Apple Developer account and remain responsible for accurate metadata and a real privacy policy. Apple reviews every app, so submitted is not approved.

FAQ

What do I need to publish an iOS app?

A paid Apple Developer account, an app built and signed for distribution, an app record in App Store Connect with a unique bundle ID, complete metadata including screenshots, a description, a privacy policy, and an age rating, an uploaded build, and a submission for App Review. Each piece has its own requirements.

How long does it take to ship an app?

The build and metadata work varies with the app, but App Review itself is usually fast, often within 24 hours once you submit. Plan extra time for TestFlight, for getting metadata right, and for any rejection that needs a fix and resubmission. Submitting is not the same as being approved.

Does AppFlight do all of this?

AppFlight runs the build, live simulator, test gate, signing, TestFlight upload, and full App Store submission from one app, and it can read a rejection, fix it, and resubmit. You bring a paid Apple Developer account and accurate metadata. Apple still reviews every app, so submitted is not approved.

Sources

Build this app without opening Xcode.

AppFlight turns a plain-English prompt into a real native iOS app and ships it to the App Store. Round 2 is open: free for your first month.

Join the waitlist