App Store Rejection Guide: Diagnose, Fix, and Resubmit
A rejection notice is a starting point, not a verdict. App Review usually names the guideline it applied, describes the problem, and sometimes attaches a screenshot. The useful work is deciding which of three buckets the issue falls into: something in your app binary, something in your App Store Connect metadata, or something in the reviewer's environment. This guide walks through prevention first, then a triage routine, then the specific guidelines that account for most rejections.
Reduce the odds before you submit
No process eliminates rejections entirely, but a few habits remove the most predictable ones.
- Read the App Store Review Guidelines end to end at least once. Every rejection traces back to that document, and knowing the shape of the rules lets you catch obvious violations during design rather than after submission. The auto-renewable subscription documentation and the in-app purchase section of the Human Interface Guidelines are worth reading before you design a paywall; the "Clearly describing subscriptions" section lists what a paywall must show.
- Test on real hardware through TestFlight. Apple has reported that more than 40% of unresolved issues relate to Guideline 2.1 App Completeness, which covers crashes, placeholder content, and incomplete information. TestFlight is the closest approximation of a reviewer's environment, so cover small home-button phones, large no-home-button phones with the Dynamic Island, and every iPad size your app supports.
- Supply a working demo account. If the app requires sign-in, create an account preloaded with realistic data and enter the credentials in App Store Connect by ticking "Sign-in required" under "App Review Information." For unusual hardware or third-party integrations, attach a short screen recording through the "Attachment" field.
- Submit ahead of your launch date. For a new app or new in-app purchases, submit at least a week before you intend to ship so there is room to absorb a rejection. For routine updates, submitting before manual testing finishes can shorten the review queue; if testing turns up a problem, pull the release and resubmit.
Triage routine for a rejection notice
Work through these steps in order; each one narrows the fix.
- Read the full guideline text the reviewer cited, not just the title. Interpretations vary between reviewers, and the surrounding clauses often explain what triggered the flag.
- Reproduce the issue. A screenshot is the fastest clue to device class or screen size; if none is attached, test the same flow on the smallest and largest supported devices.
- Classify the fix. Binary fixes require a new build. Metadata fixes (privacy policy URL, terms link, demo credentials) can ship without touching code. Environment issues usually clear on resubmission of the same build.
- Decide between fixing and appealing. If the change is small, making it is usually faster than appealing. If it would force a major redesign, appeal through App Store Connect, but expect the clock to keep running.
If the notice is unclear, you can ask follow-up questions in App Store Connect. Responses are not immediate, so budget extra days.
Privacy policy and terms of use
Guideline 5.1.1(i) requires a link to your privacy policy in the App Store Connect metadata and an easily reachable link inside the app itself. In App Store Connect, the URL goes in the App Privacy section. Inside the binary, a link in settings is generally sufficient. Since Apple relaxed the rules a few years ago the link is not expected on the paywall, though rejections on this point still occasionally appear.
Terms of use work the same way inside the app: a reachable link, not necessarily on the paywall. Metadata is the awkward part, because App Store Connect has no dedicated terms field. The workaround is to place the link in the App Store description. That link is not tappable on iOS, but it has historically satisfied review.
Minimum functionality and copycat rejections
Guideline 4.2 Minimum Functionality covers apps that look unfinished. An app that shows an empty state until the user creates data can read as incomplete; seeding sample data during onboarding presents a more normal state. A video of the app in real use can also demonstrate completeness without a new build. A thin wrapper around a website is rejected, but that does not ban web views or React Native—the requirement is an experience that feels native on a phone.
Guideline 4.1 Copycats applies when functionality and design are too close to existing apps. If you are not copying outright, review may still object that the store already has enough apps doing the same thing. The remedy is to identify a genuinely distinctive feature and either highlight it in an appeal or add it and resubmit.
App completeness: placeholders and broken links
Guideline 2.1 App Completeness is the most common source of unresolved issues. Any placeholder text such as "Lorem ipsum" visible in the app is likely to trigger an immediate rejection. If onboarding shows demo data, label it clearly as a demo and make it look realistic.
External links matter too. A link that opens Safari to a dead page is grounds for rejection, so every release should include a check—manual or automated—that all outbound links still resolve.
Ratings prompts and scam-app enforcement
Ratings help an app stand out, and Apple polices attempts to force them. Guideline 3.1.2(a) prohibits requiring users to rate or review the app, and also prohibits forcing downloads of other apps or actions like posting to social media or uploading contacts. The rationale is partly anti-fraud: these demands are common in phishing-style apps that harvest data before users discover the app is low quality. If review classifies an app as a scam, it can be pulled from the store and the developer account removed from the Apple Developer Program.
Payments outside in-app purchase
Guideline 3.1.3(a) governs when an app may use a payment method other than Apple's in-app purchase system, avoiding the 15–30% commission. Apps outside the permitted categories must use in-app purchase for all payments collected from users, and violations are rejected immediately. Even permitted apps generally may not link directly to a website for purchases; reader apps now have a limited exception that requires a special entitlement.
The permitted categories are:
- Reader apps. Apps that provide access to previously purchased digital content or full content catalogs—newspapers, books, music, streaming video. External account registration and payment links require the External Link Account Entitlement and carry restrictions.
- Multiplatform services. Users may access content bought on Android, the web, or consoles inside the iOS, iPadOS, or Mac app, but the app may not reference or link to those other purchase methods.
- Enterprise services. Apps sold in bulk to enterprise or education customers may grant access to content or services. Family bulk purchases do not qualify and must use in-app purchase.
- Person-to-person services. Real-time one-on-one services such as personal trainers, private tutors, or medical consultants may use third-party payment processors.
- Goods and services outside the app. A storefront for real-world goods and services must use a third-party processor; Apple Pay is an option for a native-feeling flow.
- Free stand-alone apps. A free companion to a paid web tool—video conferencing, email, cloud storage—does not need in-app purchase, but may not collect payments in the app or include calls to action to buy outside it.
- Advertising management apps. Apps whose sole purpose is buying and managing ad campaigns across other media do not need in-app purchase. Purchases of ads to run inside that app, such as paid boosts for social posts, still must use it.
Charging for built-in OS features
Apple does not allow charging for built-in operating system capabilities such as push notifications or iCloud storage. A frequent trigger is a subscription tier built around push notifications, justified by the server cost of supporting them. The fix is to add value-adding features that are not OS capabilities to that tier; that is usually enough for approval.
Kids category and health data
Apps in the Kids Category face extra rules: no links outside the app, and any purchasing opportunity must sit behind a parental gate. They must also comply with privacy laws worldwide covering data collected from children; Guideline 1.3 is worth reading in full.
Health data is treated with similar care. Guideline 5.1.3 Health and Health Research(ii) prohibits storing personal health information in iCloud. If you use HealthKit, you may not write false or inaccurate data, and health information may not be used for targeted advertising, marketing, or data mining.
Account deletion, private APIs, and user-generated content
Since 2022, any app that lets users create an account must also let them delete it inside the app. Apple publishes documentation on the requirement.
Private APIs are undocumented framework functions. Automated checks on submissions can flag them and trigger a rejection, and their behavior is not guaranteed—Apple can change or remove them at any time. Documented APIs are the safer choice.
Apps with user-generated content fall under Guideline 1.2, which lists four required capabilities:
- A way to filter objectionable material before it is posted.
- A way to report offensive content, with timely responses to concerns.
- The ability to block abusive users.
- Published contact information so users can reach you.
Developers have reported being told their age rating must be 17+. That is not spelled out in the guidelines, and comparable social apps sit at both 17+ and 12+, so there may be room to avoid it.
Subscription paywall rejections under 3.1.2
A 3.1.2 Business – Payments – Subscriptions rejection often functions as a catch-all for paywall design problems. These are not always spelled out in the guidelines, and you may find apps in the store with the same pattern. If the requested change is a major burden, an appeal through App Store Connect is possible, but making the change is frequently faster.
The most common version concerns how prominently the subscription price and duration are displayed. Review expects both to be prominent and legible. If a rejection says they are not prominent enough, raising contrast or font size and resubmitting is often the only change required and leaves the design intact.
Products that will not load, and purchase errors
If in-app purchases work in Sandbox and TestFlight but review cannot retrieve your products, the likely cause is that the purchases were never approved. New in-app purchases must be included in the app submission in App Store Connect. If they were included and products still fail to load, the reviewer's environment is the probable cause, and resubmitting the same build may resolve it.
A purchase error during review can originate in Apple's sandbox. The app receives STORE_PROBLEM – "There was a problem with the App Store." Check the status page for major outages, but note that sandbox can have brief outages of its own. Resubmitting, or explaining the situation to trigger a fresh review, are the usual options.
Worked example: suppose review reports a purchase failing with STORE_PROBLEM. Before changing code, check the status page. If there is a known outage, the error is environmental and a resubmission is reasonable. If there is no outage and the same build purchases cleanly in Sandbox, the reviewer's environment remains the likelier explanation. Only if the error reproduces in your own sandbox testing should you treat it as a defect in your purchase flow.
Pre-submission checklist
Run through this before every submission:
- Guidelines read, and any paywall checked against the subscription description requirements.
- TestFlight coverage across small and large phones and every supported iPad size.
- Demo credentials entered under "Sign-in required," with a screen recording attached for unusual hardware or integrations.
- No placeholder text; demo data labeled and realistic.
- Every outbound link resolves.
- Privacy policy URL in App Privacy metadata and a reachable link in the app.
- Terms of use link in the app and in the App Store description.
- Account deletion available in-app if account creation exists.
- New in-app purchases included in the submission.
- Submission timed at least a week before launch for new apps or new purchases.
Frequently asked questions
How long does an App Store rejection take to resolve?
There is no fixed timeline. Resubmitting a new build, waiting on a follow-up question in App Store Connect, or filing an appeal each adds time. Submitting at least a week before a launch target is the practical buffer for new apps and new in-app purchases.
Should I appeal or just make the change?
If the requested change is small, making it is usually faster than appealing. Appeal through App Store Connect when the change would be a major burden, and expect the review clock to keep running while the appeal is considered.
Why do my in-app purchases load in TestFlight but not for the reviewer?
The most common cause is that the in-app purchases were not included in the app submission and therefore were never approved. If they were included and still fail to load, the reviewer's environment is the likely cause and resubmitting the same build may fix it.
Where do I put a Terms of Use link if App Store Connect has no field for it?
Place the link in the App Store description field. It will not be tappable on iOS, but it has historically satisfied review. Inside the app, a reachable link—settings is typically enough—covers the binary requirement.
Can I charge for push notifications or iCloud storage?
No. Apple does not permit charging for built-in operating system capabilities. If a subscription tier is built around push notifications, add features that are not OS capabilities to that tier; that is usually enough for approval.
What does STORE_PROBLEM mean during review?
It indicates a problem with the App Store, often in Apple's sandbox environment. Check the status page for outages, then resubmit or explain the situation to trigger a new review. Treat it as your own bug only if it reproduces in your sandbox testing.