Bucket 3 · Independent service, not affiliated with Apple Inc. or Google LLC.

App Rejection Fix Pack · Guide

How should I respond to an App Store rejection message?

Reply in App Store Connect only after you know which guideline was cited and what you changed, or if you need the reviewer to clarify something specific. Keep the reply short and factual: what the reviewer saw, what you changed and where they can confirm it. If you believe the rejection is a mistake after reading the guideline carefully, you can submit an appeal to the App Review Board.

Steps to write a useful reply

  1. Note every guideline number. List each guideline cited in the message, for example 2.1, 4.3 or 5.1.1, and read the current text of each in the App Review Guidelines. Treat each one as a separate item to answer.
  2. Decide: fix, clarify or appeal. If the reviewer found a real problem, fix it. If they misunderstood a feature, a clear explanation and review notes may be enough. If you have read the guideline and still believe the decision is wrong, consider an appeal.
  3. Ask one precise question if unclear. If the message is vague, ask a specific question such as which screen showed the issue. A focused question gets a more useful answer than a general request for help.
  4. Write the reply as a short list. For each guideline, give one or two sentences: what changed, in which build, and where to find it. Avoid arguing about other apps that seem to break the same rule, since reviewers judge your app on its own.
  5. Update review notes and metadata too. Put demo account details, test steps and explanations in App Review Information so the next reviewer sees them, not only in the message thread.
  6. Resubmit the right build. Check that the build attached to the version is the fixed one before you submit for review again.
  7. Keep a record. Save the rejection text, your reply and the build number. If you appeal or get a similar rejection later, this history helps you explain your case.

A reply structure you can copy

When a done-for-you pack helps

A done-for-you pack helps when the rejection cites several guidelines, or you are unsure whether to change the app, explain it or appeal. We map each point in your notice to the guideline section, list the changes, flag issues that need product work rather than a reply, and draft the reply, an appeal text where one fits, and a resubmission checklist for you to send yourself.

US$49 all-in, one-time.
No subscription and no extra fees. Delivered by email within 24 hours of your order. Covers one rejection notice for one app.
See the App Rejection Fix Pack · US$49

Questions

When should I appeal instead of replying?

Appeal when you have read the cited guideline carefully, believe your app complies, and can explain why in specific terms. If the reviewer found a real bug or missing item, fixing it and replying is usually faster. Appeals go to the App Review Board, separate from the reviewer thread, and you submit them through Apple's appeal form.

Does pointing to similar apps on the store help?

Usually not. Reviewers assess your submission against the guidelines, and other apps may have been reviewed under different versions of the rules or for different reasons. It is more useful to explain how your own app meets the guideline, point to the specific screens, and describe the changes you made in this build.

How long should my reply be?

Short. A few lines per cited guideline is usually enough: what the reviewer saw, what changed and where to confirm it. Long replies can bury the key point. Put detailed testing instructions in the App Review Information notes, where future reviewers will also find them, and keep the message thread focused on the fix.

Contact

Email james@bucket3.ai. We reply within one business day.
Bucket 3 · bucket3.ai, 300 Sheppard Ave W, Unit 101-65, Toronto, ON M2N 1N5, Canada
See all products, refunds and contact.