![Choicely App Logo.png]](https://www.choicely.com/hs-fs/hubfs/Choicely%20App%20Logo.png?width=40&height=40&name=Choicely%20App%20Logo.png){kind=small}
How to Publish an App to the App Store (Step-by-Step 2026)
Everything after your Apple Developer account: build requirements, App Store Connect, privacy details, submission and review — with the 2026 rules that reject builds before a human sees them.
To publish an app to the App Store you need an Apple Developer Program membership ($99/year), a build made with Xcode 26 or later, an app record in App Store Connect, a complete store listing with privacy details and an age rating, and a passed App Review. Apple reviews 90% of submissions in under 24 hours. Below is the whole sequence in order, including the 2026 rules that reject builds before a human ever sees them.
Updated July 2026.
At a glance
| What | Detail |
|---|---|
| Cost | $99/year Apple Developer Program. Waivers exist for nonprofits, accredited educational institutions and government entities |
| Build requirement | Xcode 26 or later, using an iOS 26 SDK — mandatory for all uploads since April 28, 2026 |
| Machine | Access to macOS (Xcode is macOS-only) — your own Mac, a rented/cloud Mac, or a cloud build service |
| Review time | Apple reviews 90% of submissions in under 24 hours |
| Account type | Individual, or Organization (needs a D-U-N-S number, legal entity name and a working website on your own domain) |
| Two-factor | Required on your Apple Account before you can enroll |
Before you start: the account
This guide starts the moment your Apple Developer Program membership is active. If you are not enrolled yet, do that first — it is the slowest part, because Apple verifies your identity or your organization, and there is no published turnaround time for that check.
Enrolling as an organization also requires a D-U-N-S number, your exact legal entity name (not a trading name), a work email on your company's domain, and a working public website on that same domain. Social media profiles do not satisfy the website requirement.
One blocker that catches people at the next step: you cannot create an app record until your Account Holder has signed the current agreement in the Business section of App Store Connect. Check that first and save yourself a confusing dead end.
1. Build with Xcode 26 or later
Since April 28, 2026, every app uploaded to App Store Connect must be built with Xcode 26 or later, using an SDK for iOS 26 (or iPadOS 26, tvOS 26, visionOS 26, watchOS 26). Older builds are rejected at upload, before review — this is a hard gate, not a guideline.
This constrains the SDK you build against, not the versions you support. You can still set a lower deployment target and ship to older iPhones; you simply have to compile with the current toolchain. Xcode 26 itself requires a recent macOS, so plan the upgrade before submission week rather than during it.
No Mac? You don't need one. Xcode runs only on macOS, and since April 2026 it has to be Xcode 26 — which is where a lot of first-time publishers stop. Choicely builds your native iOS app for you, so neither Xcode nor a Mac is in your path. You will still need your own Apple Developer Program membership at $99/year: Apple requires an app to be submitted by whoever owns its content, which is you. Build your app free →
2. Register your Bundle ID
In your developer account, open Certificates, Identifiers & Profiles, then Identifiers, and register an App ID. Choose an Explicit App ID (one specific bundle ID, e.g. com.yourcompany.yourapp) unless you have a reason not to — Wildcard App IDs cover a family of apps but cannot use several capabilities such as push notifications. You need the Account Holder or Admin role. Your bundle ID is permanent once used, so name it deliberately.
3. Set up signing
Apple has to be able to prove a build came from you. The simple route is Xcode's "Automatically manage signing" checkbox in your target's Signing & Capabilities tab, which creates and renews what it needs. The manual route is a distribution certificate plus an App Store Connect provisioning profile — worth understanding if you build on a shared machine or in CI, where automatic signing tends to fight you.
This is the step people lose a weekend to. Certificates expire, profiles stop matching, and the error messages rarely say which. Choicely signs your build as part of producing it, so you never generate a distribution certificate by hand. See how publishing works →
4. Create the app record in App Store Connect
In App Store Connect, go to Apps and click the plus button. You will be asked for Platforms, App Name, Primary Language, Bundle ID, SKU, and User Access. Two of these deserve thought: the App Name is 2–30 characters and is what users search for, and the SKU is your own internal identifier that users never see and that cannot be changed later.
5. Upload your build
Upload from Xcode's Organizer (Archive, then Distribute App, then App Store Connect), or use Transporter, the App Store Connect API, or altool. Uploaded builds are processed before they appear for selection, so do not treat the upload finishing as the build being ready.
6. Test with TestFlight
TestFlight lets you distribute pre-release builds to up to 100 internal testers and up to 10,000 external testers. The catch worth planning around: the first build you send to an external group goes through Beta App Review, and you must supply a beta app description and review information. Internal testing has no such review, so use internal testers when you need a fast loop and external testers when you want real-world coverage before submitting.
7. Fill in the store listing
Your listing is assembled across App Information (which applies to every version) and the version page (which changes per release). Expect to provide the app name, a subtitle of up to 30 characters, keywords, a description, promotional text, your category and subcategory, a privacy policy URL, screenshots, and an age rating.
Screenshots are where most listings stall. Supply one 6.9-inch iPhone set — 1320 × 2868, 1290 × 2796 and 1260 × 2736 are all accepted — and Apple scales it down to every smaller iPhone class automatically. If your app runs on iPad, add a 13-inch set (2064 × 2752 or 2048 × 2732). You need 1 to 10 images per class, as JPEG or PNG, with no transparency. Your app icon is different: it is 1024 × 1024 and ships inside your app bundle's asset catalog, not uploaded separately in App Store Connect.
That is a lot of assets to make by hand. Screenshots at exact sizes, a 30-character subtitle, keywords, a description and a full privacy declaration — per store. Choicely's Publish Assistant generates the listing for both stores, formatted to each one's requirements. Start free →
8. Complete App Privacy and your age rating
App Privacy details — the privacy "nutrition label" — are required to submit a new app or an update. You declare what data is collected across 13 categories and why, and this must cover data collected by every third-party SDK in your app, not just your own code. Apple defines "collect" narrowly: transmitting data off the device and keeping it beyond servicing the immediate request. "Tracking" means linking your data with third-party data for targeted advertising or measurement, or sharing it with a data broker. A privacy policy URL is required.
If your app includes any of the third-party SDKs on Apple's list — Firebase, Flutter, Capacitor, Cordova, Alamofire, Lottie, OneSignal and many others — that SDK must ship a privacy manifest, and binary dependencies also need a signature. Since May 1, 2024, uploads must also declare approved reasons for certain APIs, including where a third-party SDK is what uses them.
Age ratings now use five tiers: 4+, 9+, 13+, 16+ and 18+. The older 12+ and 17+ tiers are gone, and Apple reassigned existing apps automatically from previous questionnaire answers. The questionnaire asks about in-app controls, capabilities, medical and wellness content, and violent themes.
One change to get ahead of: in July 2026 Apple added social media capability questions to the age-rating questionnaire, and from September 2026 answering them is required to submit new apps or updates. Declaring social media capabilities forces a minimum 13+ rating. If your app has social features, plan for that rating rather than discovering it at submission.
9. Submit for review
Submitting is now a "review submission" — you add your version and any related items, such as in-app purchases and subscriptions, with the Add for Review button and send them together. As of July 15, 2026, in-app purchases and subscriptions go through this same flow rather than a separate one. You can have only one app-version submission under review per platform at a time.
| Declaration | What Apple expects |
|---|---|
| Demo account | If any part of your app is behind a login, provide working credentials or a fully featured demo mode in App Review Information. Supply two-factor codes in advance in the Notes field — otherwise review can stall on contacting you |
| Export compliance | Declare whether your app uses encryption. Standard OS encryption such as HTTPS is typically exempt; proprietary encryption is not and is reviewed separately |
| Content rights | Confirm you hold the rights to all third-party content. If you stream or catalogue third-party audio or video, attach evidence in App Review Information |
For a first submission, also use the Notes field to explain what the app is for, how it makes money, and any geographic restrictions. Reviewers assess an app they have never seen before; context shortens the round trip.
10. Release
Once approved, your app moves through Waiting for Review and In Review, then either releases automatically, waits at Pending Developer Release until you release it manually, or goes out on a date you scheduled. Manual release is usually the right choice for a first launch, because it decouples "Apple said yes" from "the world can see it".
Which of these steps you still do yourself
If you build your app on Choicely, most of the sequence above stops being your problem — but not all of it, and the difference is worth being precise about.
| Step | With Choicely |
|---|---|
| Apple Developer Program membership | Yours — $99/year, in your own name. Apple requires an app to be submitted by whoever owns it |
| Build with Xcode 26 on macOS | Handled — no Mac, no Xcode |
| Bundle ID, certificates, provisioning | Handled — signed as part of the build |
| App Store Connect app record | Guided — walked through, step by step |
| Uploading the build | Handled |
| TestFlight testing | Optional — your call whether to run it |
| Store listing, screenshots, description | Handled — generated to Apple's current specs |
| App Privacy details and age rating | Prepared, you confirm — only you know what your app really does |
| Submitting for review | Guided — the submission is walked in |
| Apple's review time | Nobody's to control — 90% are reviewed within 24 hours |
| Choosing when to release | Yours |
The pattern is that Choicely removes the toolchain — the Mac, the certificates, the asset specs, the two consoles — and leaves you the decisions that are genuinely yours: your developer account, your privacy declarations, and your launch date.
The webview trap — and the template rule
The most common way a first submission fails is Guideline 4.2, Minimum Functionality. Apple expects an app to have "features, content, and UI that elevate it beyond a repackaged website", and says that if an app is not "particularly useful, unique, or 'app-like,'" it does not belong on the App Store. Guideline 4.2.2 adds that apps should not primarily be "marketing materials, advertisements, web clippings, content aggregators".
In practice this rejects the whole category of tools that wrap a website in an app shell. If you are choosing how to build, this is the single most expensive decision you will make: a wrapper can cost you the submission entirely, no matter how good your listing is.
There is a second rule that specifically catches no-code and template-built apps, and almost nobody mentions it. Guideline 4.2.6 rejects apps created from a commercialized template or an app generation service unless they are submitted directly by the provider of the app's own content. Read plainly: the business whose app it is must submit it, under its own developer account. That is why this guide starts with your own Apple Developer Program membership rather than someone else's — a builder that submits everyone's apps from its own account is the exact pattern 4.2.6 exists to stop.
Why submissions get rejected
Apple publishes real numbers, and they are more useful than the guesses in circulation. In 2025 Apple reviewed over 9.1 million submissions and rejected about 2.09 million — roughly 23%. Note what that counts: submissions, not apps. Apple states that an app may be submitted several times before it is approved, so one app can appear in that figure repeatedly. In the same year, over 387,000 submissions were approved after an earlier rejection. A rejection is a round trip, not a verdict.
Apple's own list of common causes is short and unglamorous: crashes and bugs, broken support or privacy-policy links, placeholder content, missing demo accounts or configuration, privacy policies that do not say what is collected or shared, unclear data-access requests, inaccurate screenshots, and web clippings or link collections. Apple notes that over 40% of unresolved issues relate to Guideline 2.1, App Completeness — submissions that were simply not finished.
The pattern is that most rejections are preventable in an afternoon. Fix crashes, remove placeholders, check every link, provide a demo account, and make your screenshots show the app that actually exists.
Pre-submission checklist
- Built with Xcode 26 or later against an iOS 26 SDK
- Account Holder has signed the current agreement in the Business section
- Bundle ID registered and matching your build
- No crashes on a real device, not just the simulator
- Every link works — support URL, marketing URL, privacy policy URL
- No placeholder text, no lorem ipsum, no empty screens
- One 6.9-inch iPhone screenshot set (plus 13-inch iPad if applicable), no transparency
- App Privacy details completed, including every third-party SDK
- Age rating questionnaire answered — including social media capabilities
- Demo account credentials and any two-factor codes in App Review Information
- Export compliance and content rights declared
- If you distribute in the EU, trader status provided and verified
When you don't need a builder for this
If you already have a developer on your team and a working build pipeline, you own the hard part already. Everything above is a Tuesday for you, and a builder adds nothing — keep your setup.
If your app is already finished in native code or on another platform, you need your own developer accounts and your own submission, not a builder. And if your product's core is complex custom backend logic, a development team will serve you better than any no-code tool.
Choicely is worth a look if you want to build the app and ship it in one place: you build a real native iOS and Android app free — 300 credits every month, no credit card — and the Publish Assistant pre-checks it against the rules above, generates your store listing, and walks the submission. Because Choicely builds real native apps rather than webview wrappers, the Guideline 4.2 trap above is not one you have to design around. You still hold your own Apple Developer Program membership at $99/year, which is exactly what Guideline 4.2.6 requires.
How long does App Store review take?
Apple reviews 90% of submissions in under 24 hours. That is review time only — it does not include the time to enroll in the Apple Developer Program, which is verified separately and has no published turnaround. Plan your launch date from the day your build is ready to submit, not from the day you start enrolling.
Do I need a Mac to publish to the App Store?
You need access to macOS, because Xcode only runs on macOS and Xcode 26 is now mandatory for uploads. That does not have to be your own Mac — a rented or cloud Mac, or a cloud build service, works too. If you build with Choicely, the Publish Assistant handles the build and submission, so you do not need a Mac or Xcode yourself.
Why do apps get rejected from the App Store?
Most rejections are ordinary incompleteness: crashes, broken links, placeholder content, a missing demo account for a login-gated app, or privacy details that do not match what the app does. Apple says over 40% of unresolved issues relate to App Completeness. The biggest structural reason is Guideline 4.2 — an app that is essentially a wrapped website.
What happens if my app is rejected?
You get the specific guideline cited, you fix it, and you resubmit — often without needing a new build if the problem is metadata or a declaration. Rejection is normal: in 2025 over 387,000 submissions were approved after an earlier rejection.
What are the App Store screenshot sizes in 2026?
Supply one 6.9-inch iPhone set — 1320 × 2868, 1290 × 2796 or 1260 × 2736 — and Apple scales it down to smaller iPhone classes automatically. iPad apps also need a 13-inch set, 2064 × 2752 or 2048 × 2732. Between 1 and 10 images per class, JPEG or PNG, no transparency.
Do I need TestFlight before submitting?
It is not required, but it is the cheapest insurance you can buy. TestFlight supports 100 internal testers and 10,000 external testers. Note that the first build sent to an external group goes through Beta App Review, so build that into your timeline if you plan external testing.
Can I publish to the App Store without an Apple Developer account?
No. App Store distribution requires an Apple Developer Program membership at $99/year, and Guideline 4.2.6 requires that a template-built or generated app be submitted by the provider of its content — meaning under your own account. Nonprofits, accredited educational institutions and government entities can apply for a fee waiver.
Building your app as well as publishing it? Choicely builds real native iOS and Android apps free — 300 credits every month, no credit card — and the Publish Assistant pre-checks your app against the rules above, generates your store listing, and walks the submission into both stores.
Sources & disclosure: fees, build requirements, asset specs, privacy and age-rating rules, review data and rejection statistics verified against Apple's official developer documentation and App Store transparency reporting on July 28, 2026. Choicely publishes this guide and sells an app-publishing product, so we have a commercial interest in it — the section above on when you do not need a builder is there for that reason. Store requirements change often; we re-verify quarterly.
Required footer addition
Apple, the Apple logo, App Store and App Store Connect are trademarks of Apple Inc., registered in the U.S. and other countries. Choicely is not affiliated with, sponsored by, or endorsed by Apple Inc.