How to publish an app to the App Store.
From zero to live in a week.
Every guide on how to publish an app to the App Store either skips the boring parts or buries the actual steps under screenshots of a 2018 Xcode. This one is the workflow as it stands in 2026: Apple Developer Program enrollment, bundle identifier setup, App Store Connect, screenshots, App Privacy, TestFlight, and the App Review questionnaire that decides whether your app ships in 48 hours or 48 days.
External TestFlight testers per app
What it is
What it actually means to publish an app to the App Store.
When people ask how to publish an app to the App Store, they usually mean the whole sequence from “I have a compiled .ipa” to “a stranger in another country can install my app from a search result.” That sequence has three parts: getting Apple to trust you (Apple Developer Program), getting your binary into Apple’s system (App Store Connect and signing), and getting Apple to approve the listing (App Review). None of the three are technically hard. All three have small details that send first-time submissions back to the developer.
The total real cost in 2026 is $99 a year for the developer membership, plus whatever you spend on the tooling that builds the binary. The total real time, end to end, is roughly a week for a brand-new account and a few hours for accounts that have shipped before. The rest of this guide is the step-by-step.
The 8 steps
Eight steps from compiled binary to live App Store listing.
Here is the full submission path, in order. Each step is small; the trouble comes from doing them out of order. If you are learning how to publish an app to the App Store for the first time, run through these top to bottom and resist the urge to skip ahead.
The full path from Apple Developer enrollment to a live App Store listing is eight steps. The good news for Newly users: four of them (2–5: bundle ID, certificates, listing creation, and the release build) are automated. You handle the four that only you can — the developer enrollment, the marketing copy, the optional TestFlight round, and the App Review questionnaire.
- 1
Enroll in the Apple Developer Program
Sign in at developer.apple.com with your Apple ID, pick Individual or Organization, and pay the $99/year fee. Individuals get approved in a day or two. Organizations need a D-U-N-S number and a legal entity name; expect one to two weeks. You cannot publish app to App Store without an active membership.
- 2
Register a bundle identifier
Inside the developer portal, register a unique bundle identifier (reverse-DNS format, like com.yourcompany.appname). This ID is permanent and ties your binary, signing certificates, and App Store listing together. Pick carefully — you cannot rename it after the first build is published.
Newly handles this for youNewly auto-registers a bundle ID for your project the first time you build. No reverse-DNS naming headaches.
- 3
Set up signing certificates and provisioning profiles
Generate a distribution certificate and an App Store provisioning profile. Xcode and EAS (Expo Application Services) can both handle this automatically if you grant access to your developer account. Manual setup means downloading the cert, installing it in Keychain, and matching it to a profile that lists your bundle identifier.
Newly handles this for youCloud builds via EAS generate and rotate certificates and profiles for you. You never download a .p12 or open Keychain.
- 4
Create the app in App Store Connect
At appstoreconnect.apple.com, click New App, fill in the name (up to 30 characters), primary language, bundle identifier, and SKU. This creates the listing shell. You can save and come back; nothing goes live until you hit submit at the end.
Newly handles this for youNewly creates the App Store Connect listing shell from your project metadata so you only fill in the marketing copy.
- 5
Build, archive, and upload a release binary
From Xcode (Product > Archive) or EAS (eas build --platform ios --profile production && eas submit), produce a signed .ipa and upload it to App Store Connect. Processing takes 10 to 30 minutes; you will see the build appear in the TestFlight tab once it is ready.
Newly handles this for youCloud build + EAS Submit lands the signed .ipa in App Store Connect with one click. No local Xcode archive.
- 6
Fill in metadata, screenshots, and App Privacy
Upload at least one set of screenshots (6.5-inch or 6.7-inch iPhone is the minimum), write the description, keywords (100 character limit, comma-separated), support URL, marketing URL, and privacy policy URL. Complete the App Privacy questionnaire — Apple shows a privacy nutrition label on your product page based on these answers. The App Privacy Manifest inside your binary must match.
- 7
Run a TestFlight round (optional but recommended)
Promote the build to TestFlight. Internal testers (your team, up to 100) get it instantly. External testers (up to 10,000) need a one-time beta review, usually under a day. Catch crashes here, not in App Review. Builds expire after 90 days.
- 8
Answer the App Review questionnaire and submit
Provide a demo account if any feature is behind auth (without one, reviewers cannot test and will reject). Attach review notes explaining anything non-obvious, like a feature that needs a specific input to trigger. Confirm export compliance and content rights, then submit. App Review averages 24 to 48 hours and you will get a push notification when the status changes.
Newly does 4 of the 8 steps for you.
If you are using Newly to build the iOS app itself, steps 2 through 5 are automated: the bundle identifier registration, the signing certificates and provisioning profile, the App Store Connect listing shell, and the signed .ipa upload all happen in the cloud. You still own the four steps only you can do — the $99 Apple Developer Program enrollment, the marketing copy and screenshots, the optional TestFlight round, and the App Review questionnaire. From $25/month with unlimited cloud builds.
Required vs optional
What App Store Connect actually demands.
First-time submitters often waste hours on things Apple does not require (an app preview video, ten locales of metadata, promotional artwork) and miss the things it does (a working demo account, the App Privacy Manifest). The split below is the minimum versus the nice-to-have.
Required
- Active Apple Developer Program membership ($99/year)
- Unique bundle identifier (reverse-DNS)
- Distribution signing certificate
- Screenshots at 6.5-inch or 6.7-inch iPhone size
- Privacy policy URL (publicly accessible)
- Support URL
- App Privacy questionnaire answers
- Demo account if the app is auth-gated
- Export compliance declaration
Optional
- App preview video (15 to 30 seconds per locale)
- Marketing URL (separate from support)
- Promotional text (170 characters, changeable without a new build)
- TestFlight beta round
- Localized metadata for non-default languages
- In-app events for featured promotion
- Pre-orders (lets users tap Get before launch)
- Custom product pages for ad campaigns
The optional column is where you spend time on version two. Ship version one with the required column only.
Rejection recovery
The five rejection reasons that catch first-time submitters.
A rejection is not a verdict on your app. It is App Review flagging a specific guideline number, usually with a screenshot of the screen that triggered it. Fix the issue, bump the build number, resubmit. Most teams clear a rejection in a single afternoon. The five below cover roughly 80 percent of what first-time submitters hit.
Demo account missing or broken
If any screen sits behind a login, App Review needs working credentials in the review notes. No demo account is the single most common rejection. Use a dedicated review user that does not expire and that the reviewer can reset to a known state.
Minimum functionality
Apple rejects apps that feel like a thin wrapper around a website, a single feature that belongs in a larger app, or a brochure with no interactive value. If the only thing your app does is open a webview to your homepage, expect a rejection under guideline 4.2.
Privacy policy URL missing or wrong
The URL in App Store Connect must lead to a real, publicly accessible privacy policy that matches the App Privacy answers. If the URL 404s, redirects to a login, or contradicts the privacy nutrition label, the submission fails.
Metadata mismatch
If your description promises features the binary does not include, or the screenshots show a UI different from the build, App Review flags it. Take screenshots from the exact build you upload — not from a marketing comp or an older version.
Crashes on the reviewer's device
App Review runs your binary on real hardware. A crash on launch, a white screen, or a permission prompt that immediately closes the app gets flagged. Test the same .ipa you uploaded on a clean device profile before you hit submit.
The fix loop is short: read the rejection notice, change one thing, bump the build number, upload, resubmit. Apple does not keep score, and a rejected submission does not count against future review times. If you reach four rejections on the same build, stop and read the relevant App Review guideline before the fifth — sometimes the issue is structural and a fifth upload will not help.
FAQ
Common questions about how to publish an app to the App Store.
Apple charges $99 a year for the Apple Developer Program, and that membership is what unlocks the ability to publish an app to the App Store, distribute through TestFlight, and access signing certificates. The fee renews annually; if it lapses, your apps stay live for a grace period but you cannot ship updates until you re-enroll. Organizations pay the same $99 as individuals, but enrollment requires a D-U-N-S number, which takes an extra week or two to verify. Everything else is included: App Store Connect, the developer portal, beta testing, analytics, and App Review. Apple takes a cut on paid downloads and in-app purchases (15 percent for the Small Business Program under $1M revenue, 30 percent above), but the $99 is the only flat fee.
Publish an app to the App Store without the certificate dance.
Newly handles the bundle identifier, the signing certificates, the provisioning profile, and the .ipa upload. You bring the $99 Apple Developer Program membership and the App Store Connect listing. From idea to App Review in an afternoon.