Guideline 5.6 rejection: Developer Code of Conduct
What it means, why it happens, and how developers get through it.
Subject line you may see: Guideline 5.6 - Developer Code of Conduct
What Apple's guideline says
Apps should never prey on users or attempt to rip off customers, trick them into making unwanted purchases, force them to share unnecessary data, raise prices in a tricky manner, charge for features or content that are not delivered, or engage in any other manipulative practices within or outside of the app.
From App Review Guidelines, 5.6, as revised October 16, 2026.
Common causes
- Tricky pricing, unwanted purchases, or charging for things not delivered
- Forcing people to share data they do not need to share
- Disrespectful messages to App Review, customers, or in review responses
- Repeated manipulative or misleading behavior
How to fix it
- Read exactly which behavior the message names
- Remove the practice from the app and from your marketing
- Keep every message to App Review and customers factual and polite
- If your account was terminated, Apple says you may provide a written statement of the improvements you plan to make
- Reply with what you changed
What to put in your reply
A sample reply note. Replace the brackets with your facts and remove anything that does not apply.
Hello, Thank you for the review. Regarding Guideline 5.6, we [describe the change]. Could you tell us which feature or behavior was flagged, so we can address it fully? Thank you.
Real cases: others who got 5.6
1 public case: 1 outcome unknown. Outcomes are what the developer posted.
Questions developers ask about 5.6
What does a Guideline 5.6 rejection mean?
Apple thinks the app or the developer behaves in a manipulative, misleading, or disrespectful way. It can come with account consequences, so read the message closely before you act.
Why do apps get rejected under Guideline 5.6?
Common causes, based on Apple's guideline text: tricky pricing, unwanted purchases, or charging for things not delivered; forcing people to share data they do not need to share; disrespectful messages to App Review, customers, or in review responses; repeated manipulative or misleading behavior.
How do I fix a Guideline 5.6 rejection?
1. Read exactly which behavior the message names. 2. Remove the practice from the app and from your marketing. 3. Keep every message to App Review and customers factual and polite. 4. If your account was terminated, Apple says you may provide a written statement of the improvements you plan to make. 5. Reply with what you changed.
Do I need a new build for Guideline 5.6?
Read carefully, then decide. This one depends on details. Reply asking what exactly was flagged before changing things. 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?
Reply in App Store Connect. Thank the reviewer and name Guideline 5.6, 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?
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, $12Have 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, $29Related rejections
See also: 5.6.1 review prompts · 2.5.19 hidden features
Source: Apple's App Review Guidelines, section 5.6, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.