How to upload an app to App Store Connect (2026)

What the build needs before you upload

An upload only succeeds if the binary is built for distribution and signed correctly. Before you upload, make sure you have:

• A paid Apple Developer Program membership.
• An app record in App Store Connect with a registered Bundle ID.
• A build compiled with Xcode 14 or later and a current iOS SDK. Apple requires Xcode 14 or later for App Store uploads in 2026.
• An Apple Distribution certificate and an App Store provisioning profile used to sign the build.
• A version string and a build number. The build number has to increase with every upload for the same version.

If signing is wrong, the upload is rejected at validation before it ever reaches review. For the certificate and profile side of this, see the guide on iOS provisioning profiles.

Ways to upload a build

You have four common paths, and they all deliver the same signed .ipa:

1. Xcode Organizer. After archiving, choose Distribute App and let Xcode validate and upload. This is the most direct path if you already build in Xcode.
2. Transporter. Apple's free Transporter app from the Mac App Store lets you sign in, drag in an exported .ipa, validate, and deliver. It is useful when the build was produced outside Xcode.
3. The command line. Apple's command line upload tools can deliver a build from a script, which is how continuous integration systems ship without a person clicking through a window.
4. The App Store Connect API. With an App Store Connect API key and the Transporter command line tool using JSON Web Tokens, automation can upload builds without an interactive login.

Whichever path you pick, the binary still has to be built and signed the same way. What changes is who drives the delivery.

What happens after the upload

Once the upload completes, the work is not finished. The build moves into processing on Apple servers, which usually takes a few minutes and can take up to about an hour. While it processes, it will not appear in App Store Connect.

After processing finishes:

• The build shows up under TestFlight and under your app's version.
• You may be asked to confirm export compliance for encryption before the build can be used.
• You attach the processed build to a TestFlight group for testing or to an App Store version for submission.

A finished upload is not the same as a submitted app, and a submitted app is not an approved one. Apple reviews every app before it goes live.

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 the journey to the App Store in one place. For this step, it builds the app, signs it for distribution, and uploads it to TestFlight and App Store Connect from inside the app, so you do not open Xcode or Transporter yourself. You still need a paid Apple Developer account and an app record, and you remain responsible for accurate metadata. Apple reviews every app, so submitted is not approved.