Respond to an Apple rejection

Apple rejected your app after all the work it took to get it ready. That’s frustrating. Some issues can be fixed in App Store Connect without another build, so we’d start with the exact message Apple sent. Check the item it flagged and the cited guideline before changing the app.

Reproduce what the reviewer saw

Keep the reviewer notes, screenshots, app version, build number, and guideline reference. Install the app from scratch and follow the access instructions you sent to Apple.

If the reviewer couldn’t sign in, fix the account or instructions and try them yourself before replying. You want to see what they saw.

Fix the issue Apple identified

Use the guideline number to find the more detailed check:

Review message	What to check next
2.1, app completeness	Reproduce the crash, blank screen, or missing information
4.2, minimum functionality	Check the useful experience the reviewer can reach
4.3, spam	Separate duplicate submissions from a crowded category
3.1.2, subscriptions	Check the offer, billing terms, and links
4.8, login services	Check the equivalent-login rule and exceptions
5.1.1, privacy	Read the specific message: account deletion and permission explanations need different fixes
5.1.2, AI data sharing	Check disclosure and permission before the transfer

A Metadata Rejected status may need corrected information or a response without a new build. A missing or broken feature may need code changes, a test of the full flow, and a new build.

For minimum-functionality or template concerns, show what people can actually do with your app. Tell the reviewer where to tap and what they’ll see. Rewriting the store description alone may not answer an objection to the product itself.

Reply and send the submission back

Keep your reply specific: what changed, where the reviewer can find it, and which build contains the fix.

Check every item in the submission. For each rejected item, make the fix, remove it from the submission, or resubmit it as the review instructions require. An accepted app can still be held up by another unresolved item. Before you leave, check that every item Apple flagged has been addressed, your reply explains what changed, and the submission is back in review.

If you disagree with the decision

Use Apple’s review communication and appeal channels to explain a misunderstood feature. Include steps the reviewer can follow and evidence of what happens. Say whether you disagree with how Apple applied the rule or have fixed a bug the reviewer can reproduce.

No build tool can guarantee approval.