iOS App Store Submission Checklist (2026): Build, Metadata, Review

Quick answer: Before you submit, confirm seven things: agreements and EU trader status are in place; the build uses Xcode 26 or later and has processed; name, subtitle, keywords, description, support and privacy URLs are filled in; screenshots cover the required 6.3″ iPhone slot (plus iPad 13″ for iPad apps); privacy and age rating answers are current; review notes include a demo account; and a release option is set.

Most "why can't I submit?" problems start here, not in the build.

• Apple Developer Program membership is active, and you have the Account Holder, Admin or App Manager role you need.
• Latest agreements accepted. The Account Holder accepts new agreements in the Business section of App Store Connect. Expired agreements block distribution.
• Paid Apps Agreement, tax and banking are complete if the app is paid or offers in-app purchases.
• EU trader status is provided and verified if you distribute in the European Union. Apple removes apps without it from the EU storefronts under the Digital Services Act.
• Regulated categories (banking, crypto, healthcare, gambling, air travel and similar) are submitted by the legal entity providing the service, not by an individual developer.

Apple's App Review page says that, on average, over 40% of unresolved issues relate to guideline 2.1, App Completeness: crashes, placeholder content and incomplete information. Your build is the biggest lever.

• Built with Xcode 26 or later using the iOS 26 SDK. Apple has required this for uploads since April 28, 2026; check the upcoming requirements page for the next bump.
• Version and build numbers incremented; the bundle ID matches the App Store Connect record.
• Tested on real devices running the latest iOS, and on iPad if the app runs there. Fix every crash you can reproduce.
• No placeholder content, lorem ipsum, test menus or "coming soon" screens.
• All links work, including support and privacy links inside the app.
• Privacy manifest included, with approved reasons for any required-reason APIs your code or third-party SDKs use.
• Permission prompts explain clearly why you need camera, location, contacts and other data.
• Account deletion is available inside the app if users can create an account (guideline 5.1.1(v)).
• Login services: if you offer a third-party or social login for the primary account, you also offer an equivalent option that meets guideline 4.8.
• Digital goods are sold with in-app purchase (guideline 3.1.1), and the purchases are attached to this version if they're new.
• App icon is 1024 × 1024 with no alpha channel and no baked-in rounded corners.
• TestFlight round done with at least a few people outside the team. The TestFlight guide covers internal and external testing.

These fields live on the App Information and version pages in App Store Connect. Limits come from Apple's App Store Connect reference.

Do this for every localization you ship, not just your primary language. A keyword list or subtitle that was machine-translated without review is a common weak spot.

App Store Connect accepts 1 to 10 screenshots per display size and localization, as .jpeg, .jpg or .png, with no alpha channel or transparency.

• iPhone 6.3″ is required for every iPhone app (1206 × 2622 or 1179 × 2556 portrait).
• iPhone 6.9″ is optional (for example 1320 × 2868). If you skip it, App Store Connect uses scaled 6.5″ screenshots, so the 6.5″ set becomes required.
• iPad 13″ is required if your app runs on iPad.
• Mac, Apple Watch, Apple TV and Vision Pro have their own sets if you ship there.
• Content rules: show the app in use, not just a splash or login screen (2.3.3); use fictional account data (2.3.9); keep imagery suitable for a 4+ audience (2.3.8); no names or imagery of other mobile platforms (2.3.10); make clear which features need a purchase (2.3.2).
• App previews, if you use them: up to three per display size and localization. Check Apple's current specs for length and resolution before you edit.

Full pixel tables live in the App Store screenshot sizes guide. Before uploading, drop your exports into the free screenshot size checker to catch wrong dimensions and alpha channels. The screenshot requirements guide goes deeper on each rule.

• App Privacy details describe every data type you and your third-party SDKs collect, how it's used, and whether it's linked to the user or used for tracking. See privacy labels for common mistakes.
• Tracking goes through the App Tracking Transparency prompt if you track users across other companies' apps or websites.
• Age rating questionnaire answered honestly (guideline 2.3.6). Apple's 2025 update introduced 13+, 16+ and 18+ ratings and new questions, so revisit older answers. Details are in the age rating guide.
• Export compliance answered for each build. If your app only uses encryption that's exempt from documentation, such as the HTTPS built into the operating system, you can declare it with the ITSAppUsesNonExemptEncryption key in Info.plist so you aren't asked on every upload. Check Apple's export compliance documentation for your case.
• Content rights confirmed for any third-party content, music, fonts or images.

This section is where reviewers decide whether they can actually test your app.

1. Add a contact name, phone number and email that someone monitors during review.
2. Provide a working demo account, or a fully featured demo mode, if any feature requires sign-in. Keep your backend running.
3. Explain anything non-obvious: hardware requirements, region-locked content, QR codes, paywalls, or where to find in-app purchases.
4. For updates, describe new features and changes specifically. Guideline 2.3.1(a) says generic descriptions will be rejected.
5. Attach a short screen recording if a flow is hard to reach.

• Price set (free or a price point) and countries or regions selected.
• In-app purchases and subscriptions have localized names, review screenshots and are added to the submission.
• Release option chosen: release manually, automatically after approval, or automatically no earlier than a date you set.
• Phased release turned on for updates if you want automatic updates to roll out gradually over seven days.
• Pre-orders configured, if you're using them, with a realistic release date.

1. Open the version page and confirm the correct build is selected.
2. Click through every localization and look at the screenshots in each one.
3. Open the support, privacy and marketing URLs in a private browser window.
4. Sign in with the demo account on a clean install.
5. Read the review notes aloud; would a stranger find every feature?
6. Confirm the release option, then submit.

After submission, the status moves to Waiting for Review. Apple says it typically reviews at least 50% of submissions in under 24 hours and 90% in under 48 hours; App Store review time explains what slows it down.