🍎Versions & deployments10 min readUpdated: Nov 18, 2026

How to Publish an App to the App Store: Checklist

To publish an app to the App Store you need an Apple Developer Program account, a signed build, completed questionnaires and a passed review. Here's the full checklist.

👨‍💻
Roman
AboutTheApp

Overview & context

To publish an app to the App Store, you use App Store Connect. You join the Apple Developer Program, fill in the store listing and the required documents, upload a signed build and submit the release for Apple's review. Before that, you can send the app to testers in TestFlight. Below you'll find a checklist of the steps and a list of the services that pile up around the app.

1. An Apple Developer Program account

Apps are uploaded to the App Store from an account in the Apple Developer Program, which costs 99 USD a year (charged in local currency, with prices that can vary by region). You need an Apple Account with two-factor authentication to enroll. An individual shows up in the store under their own name, an organization under its legal entity name.

For an organization, Apple requires a legal entity, a D-U-N-S Number, an email on the organization's domain, a public website and a person with the authority to act for the organization. A D-U-N-S Number is free in most countries. If you publish for a company or a client, enroll as an organization right away, so the developer isn't listed as the seller. Apple verifies organizations. The details are on its enrollment page.

2. Source code, build and code signing

Your source code is probably in a repository already, for example on GitHub or GitLab. The production build of an iOS app should come out of CI, not a developer's laptop. A native app is built in Xcode (with xcodebuild archive) and Flutter has flutter build ipa. Building for iOS needs macOS, so CI needs a macOS runner, for example in GitHub Actions or Codemagic.

If your app is built with Expo or React Native, EAS Build builds it in the cloud, so you don't need a Mac of your own, and EAS Submit sends it to App Store Connect. The builds, submissions and credentials then live in your project on https://expo.dev.

Apple publishes the current build requirements on its upcoming requirements page. Since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26 SDK. Since September 9, 2026, they must also target iOS 13 or later.

The build is signed with a distribution certificate and a provisioning profile from your account. Xcode can also manage them automatically. Keep the certificate, its private key and the App Store Connect API key for CI in a password manager and in CI secrets, never in the repository.

3. Push notifications and Sign in with Apple

Push notifications on iOS always go through the Apple Push Notification service (APNs). If you send them through Firebase Cloud Messaging, you upload an APNs authentication key from your Apple Developer account to your Firebase project. The same Firebase project can also host Crashlytics, Analytics or Authentication.

If users sign in with a third-party account such as Google or Facebook, guideline 4.8 of the App Store Review Guidelines says the app must also offer a login that collects only a name and an email and lets users hide the email. Sign in with Apple is the usual way to meet it. Apps that use only their own account system are exempt.

4. Testing before you submit for review

iOS beta builds are tested in TestFlight. You can send an uploaded build to your own team first and then to external testers (see the article on TestFlight beta testing). External testing also goes through an Apple review, so plan it ahead.

If the app has a login, you have to give Apple a working demo account and keep your backend running or offer a built-in demo mode. You enter the details under App Review Information in App Store Connect. Without them, Apple can't test the release.

Test on a real device

Run the main flows on a real iPhone before you submit, not just in the simulator. After every change, use a [smoke test checklist](/guides/smoke-testing).

5. Privacy: policy, privacy details and account deletion

Apple requires a link to a privacy policy for every app. The link has to be in App Store Connect and also reachable inside the app. The policy explains what data you collect, what you use it for, who you share it with and how long you keep it. If people in the EU use your app, it also covers your GDPR information duty.

In App Store Connect you also fill in the app's privacy details, which become the privacy labels on your store page. Include the data collected by third-party libraries too. If your app or its libraries use certain system APIs, you have to give approved reasons for them in a privacy manifest file, otherwise a new or updated build won't upload to App Store Connect.

If users can create an account in the app, they must be able to delete it there as well. For services that process personal data for you, GDPR requires a data processing agreement, which large services let you accept in your account settings. This overview isn't legal advice, so have a lawyer check the actual wording of your documents.

6. What to prepare for App Store Connect

Before you create the app in App Store Connect, get the build, the graphics and the texts ready. Without them you can't submit the release for review.

Task listClick to toggle

7. App Review and how to release

After you submit the release, Apple reviews it against the App Store Review Guidelines. A rejection arrives in App Store Connect with the reason the app breaks the guidelines. After you fix it, you submit the same release again. Common reasons are a missing or broken demo account, a privacy policy link that doesn't lead to a page and privacy details that don't match the app.

Check the expected review time in App Store Connect when you submit and leave some slack before your deadline. For the production release after approval, you can choose a manual release, an automatic release as soon as the app is approved or a release from a date you pick.

9. After approval: phased release and updates

A phased release rolls an update out over seven days to users who have automatic updates on, starting at 1% on day one and reaching 100% on day seven (see App Store Connect Help). You can pause it. Users who update manually get the new version right away. Meanwhile you watch for problems in Sentry or Crashlytics.

Every update goes through the same review as the first release. Before you upload, increase the build number and the version, as described in the article on app versioning. The What's New in This Version field is shorter than full release notes, which you record in AboutTheApp under Product versions → Add version. A GitHub Actions step can record them for you. If you also ship on Android, see how to publish an app to Google Play.

Frequently asked questions

How much does it cost to publish an app on the App Store?

The Apple Developer Program costs 99 USD a year, charged in local currency. The price can vary by region. Uploading individual apps costs nothing extra. Apple offers a fee waiver to accredited educational institutions.

How long does App Store review take?

Apple doesn't promise a fixed time. Check the expected time in App Store Connect when you submit. It's usually a matter of days. For a first release, leave slack for a possible rejection and a fix. A rejection comes with the number of the guideline the app broke.

Can I publish an iOS app without a Mac?

Yes, if a cloud service or CI builds the app for you. EAS Build builds an Expo app and EAS Submit sends it. GitHub Actions or Codemagic run the build on a macOS runner. You still need an Apple Developer Program account.

Do I need a company to publish on the App Store?

No. You can enroll as an individual, but the store then lists your name as the seller. An organization needs a legal entity, a D-U-N-S Number, an email on its own domain and a public website.

Why did Apple reject my app?

You'll find the reason in the message in App Store Connect. Common ones are a missing demo account for a login, a broken privacy policy link, privacy details that don't match the app and no way to delete an account. Fix the issue and submit the release again.

Which links should I keep for an iOS app?

All of them: the repository, the CI pipeline or Expo project, the app in App Store Connect, TestFlight, Firebase, error monitoring, the password manager entry with the certificate and the legal documents. In AboutTheApp you store them with the app in categories and mark each link as public or private.

In short

Publishing to the App Store is mostly preparation: create the account, build and sign the app, test it in TestFlight, fill in the required details and questionnaires and prepare the store listing. Keep the links to every service around the app in AboutTheApp, so your team, testers and users find them in one place.

AboutTheApp

Want all your app's services in one place?

Create a free app in AboutTheApp and add links to your repository, App Store Connect, TestFlight, monitoring and legal documents.