iOS App Store Submission 2026: How to Not Get Rejected

I've submitted somewhere north of 60 apps to the App Store over the years, and I still get rejections. Not as often as I used to, but Apple's review process has a way of humbling you right when you think you've got it figured out.

The good news: Apple reviews 90% of submissions within 24 hours now. The bad news: about 40% of apps face at least one rejection during their first submission. Most of those rejections are completely avoidable if you know what the review team is looking for.

The Most Common Rejection Reasons (And How to Avoid Them)

1. Bugs and Crashes

This sounds obvious, but it's still the number one rejection reason. Apple's review team tests your app on actual devices, and they're not gentle about it. They'll tap things rapidly, rotate the device mid-action, go offline and come back, and generally try to break things.

Before you submit:

• Test on actual devices, not just the simulator. The simulator lies.
• Test on the oldest device your app supports. If you claim to support iPhone SE, test on an iPhone SE.
• Kill the app mid-task and relaunch. Does it recover gracefully?
• Test with poor network conditions. Apple's Network Link Conditioner tool is your friend here.
• Test with the device language set to something other than English. Layout issues love to hide in longer translations.

2. Incomplete Information or Placeholder Content

Apple will reject you if your app has "Lorem ipsum" text, test data, placeholder images, or broken links. They'll also reject you if your app description doesn't accurately reflect what the app does.

I once got rejected because a settings screen had a "Coming Soon" label on a feature. Apple's position: don't reference features that don't exist yet. Remove the menu item entirely if the feature isn't ready.

3. Privacy Issues

This has become a much bigger deal since Apple doubled down on privacy. Common mistakes:

• Not including a privacy policy. Required for every app. Must be accessible both in the app and on your App Store listing.
• Requesting unnecessary permissions. If your recipe app asks for camera access, you'd better have a good reason (like scanning barcodes). Apple will ask why.
• Missing purpose strings. Every permission request needs a clear, specific explanation. "We need access to your photos" will get rejected. "Select a profile photo from your library" will pass.
• Incorrect privacy nutrition labels. The data collection disclosures in App Store Connect must match what your app actually collects. Apple verifies this, and inconsistencies trigger rejection.
• ATT compliance. If your app tracks users across other apps or websites (which includes most analytics and advertising SDKs), you need the App Tracking Transparency prompt. No exceptions.

4. Design and UI Issues

Apple cares about user experience more than any other app store. They'll reject apps that:

• Don't support the latest iPhone screen sizes (including Dynamic Island)
• Have text that's too small to read
• Use non-standard UI patterns that confuse users
• Don't support Dark Mode (not strictly required, but increasingly expected)
• Have broken layouts in landscape orientation (if you support landscape)

The Apple Human Interface Guidelines aren't just suggestions. Read them. Specifically the sections on navigation, modality, and system capabilities. You don't have to follow them religiously, but you need to know the rules before you break them.

5. In-App Purchase Requirements

This is the one that catches experienced developers off guard. Apple's rules about what must use In-App Purchase (IAP) are strict:

• Digital content or services consumed within the app? Must use IAP.
• Physical goods or services performed outside the app? Can use your own payment processor.
• Reader apps (Netflix, Spotify, Kindle)? Can't include any link or reference to external purchase options. Users have to figure that out on their own.

The EU Digital Markets Act has loosened some of these restrictions for EU users, but globally, the IAP requirement remains. Don't try to work around it — Apple's review team knows every trick.

The Submission Process: Step by Step

Let me walk through this practically, because Apple's documentation sometimes assumes you already know things.

Before You Touch App Store Connect

1. Apple Developer Program membership — $99/year. No way around this.
2. Provisioning profiles and certificates — set these up through Xcode. Use automatic signing unless you have a specific reason not to.
3. Build your archive — In Xcode: Product → Archive. Make sure you're building for "Any iOS Device," not a specific simulator.
4. Validate before uploading — Xcode's Organizer has a "Validate App" button. Use it. It catches some issues before Apple ever sees your app.

In App Store Connect

Here's what you need to have ready:

• Screenshots: Required for 6.7" (iPhone 15 Pro Max), 6.5" (iPhone 11 Pro Max), and if you support iPad, 12.9" screenshots. You need between 1 and 10 screenshots per size. Make them count — these sell your app.
• App description: 4,000 character limit. Front-load the important stuff because most people won't read past the first paragraph. Avoid keyword stuffing.
• Keywords: 100 characters total, comma-separated. Don't repeat words already in your title or subtitle — Apple indexes those automatically.
• Privacy policy URL: Must be a live, accessible link.
• Support URL: A real page where users can get help. Not a generic homepage.
• App Review notes: This is your chance to talk directly to the reviewer. Include demo account credentials if your app requires login, explain any unusual functionality, and pre-emptively address anything that might confuse a reviewer.

The Review Process

After you hit "Submit for Review," here's what happens:

1. Waiting for Review: Usually a few hours, occasionally up to 24 hours.
2. In Review: A human reviewer (yes, actual humans) tests your app. This typically takes 24–48 hours.
3. Approved or Rejected: If rejected, you'll get a specific reason and often screenshots showing the issue.

If you're rejected, don't panic. Fix the issue, respond in the Resolution Center explaining what you changed, and resubmit. Resubmissions usually get reviewed faster. And be polite in the Resolution Center — the reviewers are people, and a courteous response goes further than an angry one.

App Store Optimization (ASO): Getting Found

Getting approved is only half the battle. Now people need to find your app. ASO is basically SEO for the App Store, and it's wildly underutilized.

Title and Subtitle

Your title has 30 characters, your subtitle has 30 characters. These are the two most important fields for search ranking. Include your primary keyword naturally. "Budgetly — Expense Tracker" works. "Budget Money Finance Expense Track" does not.

Keywords Field

100 characters of comma-separated keywords. Some tips that actually help:

• Use singular forms (Apple matches plurals automatically)
• Don't include your app name or category name
• Don't use spaces after commas — waste of characters
• Include common misspellings of relevant terms
• Use Apple Search Ads' keyword research tool — it's free and shows actual search volume

Screenshots and Preview Videos

Your first three screenshots are visible without scrolling in search results. Make them your strongest selling points. Show the app doing something impressive, not a splash screen or login page.

App preview videos (up to 30 seconds) boost conversion significantly — apps with preview videos see 20–35% higher conversion rates on average. Keep them focused on the core value proposition. Nobody watches a 30-second intro animation.

Ratings and Reviews

Apps with higher ratings rank higher. Use Apple's SKStoreReviewController to prompt for reviews at the right moment — after a user has completed a meaningful action and had a positive experience. Don't prompt on first launch. Don't prompt after a frustrating error. Apple limits the prompt to three times per year per user, so make each one count.

Updates and Ongoing Maintenance

Your first submission is the hardest. After that, updates go through the same review process but tend to get approved faster (usually within 24 hours). A few maintenance tips:

• Submit updates regularly — at minimum when new iOS versions launch
• Respond to user reviews, especially negative ones. It shows Apple (and users) that you're actively maintaining the app
• Watch for deprecation notices from Apple. They regularly remove apps that haven't been updated in a long time or that use deprecated APIs
• Keep your provisioning profiles and certificates current. Expired certificates mean you can't submit updates

The App Store review process isn't arbitrary — it's predictable once you understand what Apple cares about. Build a quality app, respect user privacy, follow the guidelines, and be thorough in your submission materials. Do those things, and you'll spend a lot less time in the rejection-fix-resubmit cycle and more time watching your download numbers climb.