How to respond to an App Store rejection

Start with the exact review message

Save Apple’s complete message, the guideline numbers it mentions, the app version and build, and the date of the review. Keep earlier replies in order. A reviewer’s report of a crash and a crash you have reproduced are different facts; record each with its source.

Collect the metadata for that submission and actual screenshots of relevant pages. Add the navigation path, account state and prerequisites for each screen. If Apple asks about deletion, for example, one settings screenshot is insufficient to explain the entire deletion flow.

Create one actionable record per issue

For each concern, write the reported behavior, the evidence that supports it, the behavior you expect, and the steps someone must follow to check it. Include the device and operating system when known. Mark missing details as unknown rather than filling them in.

Give the developer a specific change and an acceptance check. “Improve subscriptions” is too broad. “Open the paywall from Settings, confirm the displayed duration and price match the selected product, then verify purchase and restoration in the intended test environment” is a useful verification task. Only use it when subscriptions are relevant to the actual review.

Verify the build before claiming a fix

Test the exact build you intend to submit. Record what you tested, the result, the account prerequisites, and any remaining limitations. A successful local build does not prove the reviewer can reach a backend, complete a purchase or access a restricted feature.

If a fix is unfinished, retain a placeholder in your draft. Do not send a sentence claiming that an issue has been resolved merely because an AI tool suggested a solution.

Use a short English response

Dear App Review Team,

Thank you for reviewing [APP NAME], version [VERSION], build [BUILD].

Regarding [GUIDELINE / SPECIFIC QUESTION]:
[Describe the verified change or answer the question directly.]

To verify:
1. [Prerequisite or starting screen]
2. [Exact navigation and action]
3. [Expected result confirmed in this build]

[Identify the attached screenshot or recording, if supplied.]

Thank you.

Replace every bracketed field before sending. Supply test account credentials only through the intended private App Store Connect fields, never in a public guide, screenshot or analytics event.

Choose the next review step using Apple’s instructions

Read the specific message in App Store Connect to determine whether Apple needs additional information, revised metadata or a new build. When you disagree with a finding, explain the relevant facts and consult Apple’s available review and appeal options. An appeal and an ordinary reply are separate actions.

Use Apple’s App Review guidance and Apple’s current App Review Guidelines as the authoritative references. This guide describes a preparation workflow; it cannot predict approval or replace Apple’s decision.