Rejection Decoder
Home / Guidelines / 5.6.1

Guideline 5.6.1 rejection: App Store Reviews (custom rating prompts)

What it means, why it happens, and how developers get through it.

Subject line you may see: Guideline 5.6.1 - Legal - App Store Reviews

In one line: Your app asks for a rating with its own prompt instead of Apple's system review prompt. Guideline 5.6.1 says to use the provided API, and custom review prompts are not allowed.
Usual next move: Fix, new build, then replySomething in the binary has to change. Fix it, bump the build, resubmit, and reply with what changed and how to verify.Based on how this guideline is usually resolved, not a prediction for your app.
Paste your rejection to check
On this page: CausesFixReplyReal casesQuestions

Common real causes

How to fix it

  1. Remove every custom rating screen, star picker, and pre-prompt question, including ones added by a library or remote config
  2. Ask only through the system prompt: RequestReviewAction in SwiftUI or the StoreKit requestReview API (SKStoreReviewController is deprecated)
  3. Call it after a completed task, not from a button: the system may show nothing, and shows it at most three times in 365 days to someone who has not rated
  4. Never gate features, content, or rewards on a rating
  5. In your reply, say which screen you removed and where the system prompt is now called

What to put in your reply

Thank them and name Guideline 5.6.1.
Say exactly what changed, and in which version and build.
Give a numbered path the reviewer can follow.
Attach proof: screenshots or a screen recording.

The full fill-in-the-blanks reply for 5.6.1 is in the Rescue Kit.

Real cases: others who got 5.6.1

No public cases logged yet.

Questions developers ask about 5.6.1

What does a Guideline 5.6.1 rejection mean?

Your app asks for a rating with its own prompt instead of Apple's system review prompt. Guideline 5.6.1 says to use the provided API, and custom review prompts are not allowed.

Why do apps get rejected under Guideline 5.6.1?

The most common real causes: A custom 'Rate us' alert or star picker that sends people to the App Store; A rating screen in onboarding or right before the paywall; A 'Do you like the app?' step that sends only happy users to the review prompt; requiring a rating or review to continue or unlock content (Guideline 3.2.2(x) also forbids this); public replies to App Store reviews that include personal information, spam, or marketing.

How do I fix a Guideline 5.6.1 rejection?

1. Remove every custom rating screen, star picker, and pre-prompt question, including ones added by a library or remote config. 2. Ask only through the system prompt: RequestReviewAction in SwiftUI or the StoreKit requestReview API (SKStoreReviewController is deprecated). 3. Call it after a completed task, not from a button: the system may show nothing, and shows it at most three times in 365 days to someone who has not rated. 4. Never gate features, content, or rewards on a rating. 5. In your reply, say which screen you removed and where the system prompt is now called.

Do I need a new build for Guideline 5.6.1?

Fix, new build, then reply. Something in the binary has to change. Fix it, bump the build, resubmit, and reply with what changed and how to verify. This is how the guideline is usually resolved, not a prediction for your app.

How should I reply to App Review about Guideline 5.6.1?

Reply in App Store Connect. Thank the reviewer and name Guideline 5.6.1, say exactly what changed and in which version and build, give a numbered path the reviewer can follow, and attach proof such as screenshots or a screen recording.

Stuck on 5.6.1?

Do it yourself, faster

App Store Rejection Rescue Kit: the full decoder, 12 reply templates, Notes for Review templates, and a 60-point preflight checklist.

Get the kit, $12

Have it written for you

Send your rejection, get a reply drafted for your exact case. Kit buyers get $10 off.

AI-assisted, built on Apple's App Review Guidelines. Not a guarantee of approval. If we do not deliver within 24 hours, you get a full refund.

Reply service, $29

Related rejections

2.1(a) App Completeness2.1(b) In-app purchases not found2.5.2 Downloading or executing code2.5.19 Hidden or undocumented features

Source: Apple's App Review Guidelines, section 5.6.1, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.