Getting through iOS app review
A rejection late in a release cycle is costly: the schedule is already tight, and every extra round trip pushes the launch back. The process itself is not yours to remove, but the number of avoidable rejections is partly within your control. This guide covers what to read before you build, where in-app purchases usually go wrong, and how to pick a response once a rejection lands.
Read the App Review Guidelines before you build
A rejection normally names the guideline the app is said to break, which makes the App Store Review Guidelines the first document worth knowing. The full text is long and not applied with perfect consistency, but familiarity with it lets you catch problems while they are still cheap to fix.
If the plain document is hard to finish, the comic-book version pairs the guidelines with unrelated imagery. Treat it as a memory aid rather than a current reference: the guidelines change, so check the change history for dates and diffs. Also read the iOS Developer Program information and the Paid Applications Agreement available through iTunes Connect, because both contain restrictions that can lead to rejection.
Study the common rejection patterns
Apple publishes a Common App Rejections tracker that shows where most apps run into trouble and gives examples of typical rejections. Use it as a map of the ecosystem's weak points and as a checklist for your own release.
Community accounts add colour to the pattern. App Review Watch collects and shares stories about peculiar or unfair rejections, and App Review Observer tracks and publicizes odd cases. These accounts are useful for spotting recurring themes, not for predicting your own outcome.
Submit early and keep testing
If the App Store is central to your business, build review time into the schedule. When a build could plausibly ship, run a quick sanity check and submit it. You can then use the waiting days for in-house testing: if you find a problem, pull the submission and send a new build; if not, you are already further along.
Review duration is not published by Apple. Developers have long shared their own times, first through an informal #iosreviewtime hashtag and later through the crowdsourced Average App Store Review Times. Use such estimates as planning input, not as a guarantee.
Prepare your in-app purchase situation
In-app purchases are a frequent rejection source because they are complicated to configure and easy to implement incorrectly. Three failure modes recur:
- Products not available to the reviewer. On a first version, new IAP products must be attached to the submission through the iTunes Connect new release configuration. On a new version of an already released app, any new IAPs must already be submitted and cleared for sale, even if the live version does not support them.
- Wrong validation environment. Apps that use Apple's /verifyReceipt endpoint sometimes point only at the production IAP environment in the release build or backend. Reviewers test in the sandbox environment, so that configuration fails review.
- Improper legalese or metadata. Apple has tightened scrutiny of the in-app purchase flow, especially for subscriptions, and many developers have received rejections citing the Paid Applications Agreement, Schedule 2, Section 3.8(b).
A useful way to read these three is as a readiness test: can the reviewer see the product, can the reviewer complete a purchase in sandbox, and does the purchase screen meet the disclosure rules?
Understand the rejection before you respond
A rejection will arrive eventually, and possibly several times over an app's life. The first job is diagnosis, not reaction. Open the document the rejection cites, work through the specific clause, and then look at how other developers have dealt with the same clause in practice. That habit gradually turns a vague sense of unfairness into a working model of where the line actually sits, which is what makes future submissions smoother.
Choose the right response
For most rejections, the cheapest resolution is simply to make the requested change. That can feel like letting someone with little stake in your product dictate its design, but compliance is usually the shortest route to release. Save the argument for the narrower case where the reviewer appears to have misread what the app does or misapplied a rule.
Use this decision table to pick a path:
A pre-submission checklist
Before you press submit, confirm each of these:
- You have read the current App Store Review Guidelines and checked recent changes.
- You have reviewed the common rejection patterns against your own build.
- Every new IAP product is attached to a first submission, or already cleared for sale on a version update.
- Your release build and backend can validate purchases in the sandbox environment.
- Your purchase screen and metadata meet the Paid Applications Agreement disclosure requirements.
- Your schedule leaves room for review time and for a resubmission if needed.
Worked example: a first-version submission with a subscription
Suppose you are shipping version 1.0 of a subscription app. You have configured the subscription in iTunes Connect, but you have not attached it to the submission. The reviewer opens the app, cannot find the product, and rejects it. The fix is not a code change: attach the new IAP to the submission through the new release configuration and resubmit.
Now suppose the same app is at version 2.0 and adds a new annual plan. The live 1.0 build does not support that plan, but the new IAP still has to be submitted and cleared for sale before the 2.0 submission. Separately, if your backend only calls the production validation environment, the reviewer's sandbox purchase will fail even though the product is visible. Both problems are configuration issues, and both are cheaper to catch before submission than after rejection.
Treat review as a recurring cost
Nothing suggests App Review is going away, even though turnaround has improved in recent years. Budgeting a little attention to the process on every release — the current guidelines, the recurring rejection patterns, and the purchase configuration — tends to compound into fewer surprises over time.
| Situation | First move | Why |
|---|---|---|
| The request is reasonable and the change is feasible | Make the change and resubmit | Usually the fastest path to release |
| The reviewer misunderstood what the app does | Send a kindly worded, straightforward explanation of what was missed and why there is no violation | A clear oversight may be cleared for sale |
| You believe the rule itself is being interpreted incorrectly or applied unevenly | Expect messaging to rarely help | Escalation through the same thread is unlikely to change the outcome |
| You are in a messaging loop and are offered a call | Decline and work from the written rejection | The call tends to restate the thread rather than resolve it |
| You cannot compromise and see no other option | Change the major version number, recreate the release in iTunes Connect, and resubmit | A new reviewer may see it, but previous rejections may still influence the decision |
Frequently asked questions
What should I do first when my app is rejected?
Read the rejection and the document it cites, then read the cited section again. Search for how other developers handled the same issue. That usually tells you whether the fix is a code change, a configuration change, or a clarification to the reviewer.
Why does my in-app purchase fail in review but work in my own testing?
Reviewers test purchases in the sandbox environment. If your release build or backend points only at the production IAP environment for Apple's /verifyReceipt endpoint, the reviewer's purchase will fail. Check that sandbox validation is reachable from the submitted build.
Do I need to attach new in-app purchases to a version update?
Yes. On a new version of an already released app, any new IAPs must already be submitted and cleared for sale, even if the live version does not support them. On a first version, the new IAP products must be attached to the submission through the iTunes Connect new release configuration.
Is it worth taking the reviewer's offer of a phone call?
Usually not. The call tends to restate the written thread rather than change the outcome. Reading the rejection and making the appropriate change is generally a better use of time.
When should I resubmit a new version instead of appealing?
Only as a last resort, when you cannot compromise and see no other path. It requires changing the major version number and recreating the release in iTunes Connect. A new reviewer may see it, but previous rejections may still influence the decision.