App Store 5.6.1 rejection: Review prompts and customer replies
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad apps using custom rating prompts or inappropriate replies to App Store reviews.
A request for a rating is part of the reviewed experience. Guideline 5.6.1 requires Apple’s provided review API and prohibits custom review prompts. It also asks developers to respond respectfully to customer reviews without personal data, spam, or marketing.
Check prompts and public responses
Inspect every rating prompt, including those added by libraries or shown after a milestone. We’d check campaigns and remote configuration so an old custom prompt can’t reappear.
Review public replies for unrelated promotion or information that could identify the customer.
Use the supported flow
Replace custom review prompts with the provided API and remove inappropriate reply content through the store’s supported tools. Keep responses focused on the customer’s issue. Also check 3.2.2(x) for forced ratings or reviews.
Test the updated prompt path without submitting artificial reviews. Tell Apple which component changed and how the prompt is invoked. For a response-related issue, explain the correction to the support process as well as the edited text.
Messages this guide can help with
App Store 5.6.1 rejection; app store 5.6.1 denial; Guideline 5.6.1; Review prompts and customer replies
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Apple App Review guideline 5.6.1 Checked 22 September 2026