iOS
App Store Review Guidelines: How to Avoid the Most Common iOS App Rejections
Apple's current build requirements and the review guidelines that matter most, from app completeness and privacy to payments and minimum functionality.
Every app and update on the App Store goes through Apple's App Review. Most rejections aren't mysterious: Apple publishes its rules, and it publishes the most common problems too. If you build with those in mind from the beginning, submission is far less stressful. This guide covers Apple's requirements as of October 2026, and Apple's documents should always be your final reference.
Build requirements
Apple sets a minimum toolchain for apps uploaded to App Store Connect:
- Since April 28, 2026, apps must be built with Xcode 26 or later, using an SDK for iOS 26, iPadOS 26, tvOS 26, visionOS 26 or watchOS 26.
- Since September 9, 2026, iOS and iPadOS apps must target iOS 13 or later.
- Starting April 2027, iOS and iPadOS apps must be built with the iOS & iPadOS 27 SDK or later, and target iOS 15 or later.
That April 2027 change is worth planning for now. Check your supported iOS versions and libraries, since a dependency that lags behind can hold up an urgent update.
How long review takes
Apple says review typically covers at least 50% of submissions in under 24 hours and 90% in under 48 hours. Incomplete submissions can take longer. Don't plan a launch around the shortest case. Leave time for one rejection and one resubmission. Apple offers expedited review for critical bug fixes and time-sensitive events, but treat that as an exception rather than a schedule.
The biggest cause: app completeness
Apple reports that about 40% of unresolved issues fall under guideline 2.1, App Completeness. The common problems are ordinary and preventable:
- Crashes and bugs. Test on the latest OS versions.
- Broken links. Your app needs a working support link and privacy policy link.
- Placeholder text and images left in the build.
- Missing review information, such as a demo account or setup steps.
- In-app purchases that the reviewer can't find or that don't work.
If your app has a login, give Apple a working demo account and keep the back-end service on during review. If a feature needs special hardware or is hard to reach, add notes or a demo video. Reviewers can only approve what they can see. A surprising number of delays come down to an expired test account.
Accurate metadata
Your description, screenshots and previews must reflect the app's real experience. App names are limited to 30 characters, and keywords shouldn't be stuffed with trademarks or popular app names. Screenshots should use fictional account details, not real people's data. New features should be described specifically in the Notes for Review field, since Apple's guidelines warn that generic descriptions are rejected.
Privacy
Privacy is where a rejection is often a real design problem instead of a quick fix:
- Link a privacy policy in App Store Connect and in the app. It must explain what you collect, how, and all uses, along with retention and deletion.
- Complete privacy details in App Store Connect, including data collected by third-party SDKs. You're responsible for keeping them accurate.
- Get consent before collecting user or usage data, and write clear purpose strings for permissions.
- Request only data relevant to core functionality.
- If the app supports account creation, offer account deletion within the app.
- Don't require a login unless the app has significant account-based features.
- Tell users when personal data goes to third parties, including third-party AI, and get explicit permission first.
- Use App Tracking Transparency for tracking.
Audit every SDK before submission. Apple's definition of tracking can include an SDK that combines your users' data with data from other apps for ads, even if you don't use it for that purpose.
Payments
Under guideline 3.1.1, unlocking features or digital content, including subscriptions and premium content, must go through In-App Purchase. You can't use your own license keys or QR codes for that. Apple's rules on external purchase links vary by storefront, and that area has changed recently, so check the current text for each market you serve. Purchases that can be restored need a restore mechanism. Purchased credits may not expire.
Minimum functionality
Guideline 4.2 says apps should offer more than a repackaged website, and apart from catalogs, they shouldn't primarily be marketing materials, web clippings or collections of links. Apple also says that apps created from commercial templates or app-generation services are rejected unless the content provider submits them directly. If your app is a thin wrapper around your site, add something that truly earns its place on the device, or consider a web app instead.
User content and login
Apps with user-generated content or AI content creation need filtering, a way to report offensive content with timely responses, the ability to block abusive users, and published contact information. If you use a third-party or social login as your primary account login, guideline 4.8 generally requires an equivalent option that limits data collection to name and email and lets people keep their email private.
Who submits matters
Apps in regulated fields such as banking, healthcare or gambling generally must be submitted by the legal entity providing the service. That can decide whose developer account you use, so settle it early. It's also good practice for a business to hold its own Apple Developer account, rather than relying on a vendor's.
If you're rejected
Read the message in App Store Connect, which references the specific guideline. Fix the issue, reply, and resubmit. If you believe App Review misunderstood your app, you can appeal to the App Review Board, giving specific reasons your app complies. Apple allows one appeal per rejected submission, and you can also book an appointment to discuss guidelines. Stay factual and specific. Clear explanations get further than frustration.
Our team can help you prepare your iOS app for review and handle the submission.