Guideline 2.3.2 rejection: In-app purchases not disclosed in metadata
What it means, why it happens, and how developers get through it.
Subject line you may see: Guideline 2.3.2 - Performance - Accurate Metadata
What Apple's guideline says
If your app includes in-app purchases, make sure your app description, screenshots, and previews clearly indicate whether any featured items, levels, subscriptions, etc. require additional purchases.
From App Review Guidelines, 2.3.2, as revised October 16, 2026.
Common causes
- Screenshots feature premium content with no note that it needs a purchase
- The description lists paid features as if they were free
- Promoted in-app purchases with a display name, image, or description not suitable for a public audience
How to fix it
- Mark which featured items need a purchase in the description
- Add a short note on screenshots or previews that show paid content
- Check promoted in-app purchase names, images, and descriptions
- Reply listing the fields 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 2.3.2, we updated the description and screenshots to state that [features] require an in-app purchase. Changed fields: [description, screenshots 2 and 3]. Thank you.
Real cases: others who got 2.3.2
No public cases logged yet.
Questions developers ask about 2.3.2
What does a Guideline 2.3.2 rejection mean?
Your description, screenshots, or previews show paid items, levels, or subscriptions without saying they cost extra.
Why do apps get rejected under Guideline 2.3.2?
Common causes, based on Apple's guideline text: screenshots feature premium content with no note that it needs a purchase; the description lists paid features as if they were free; promoted in-app purchases with a display name, image, or description not suitable for a public audience.
How do I fix a Guideline 2.3.2 rejection?
1. Mark which featured items need a purchase in the description. 2. Add a short note on screenshots or previews that show paid content. 3. Check promoted in-app purchase names, images, and descriptions. 4. Reply listing the fields you changed.
Do I need a new build for Guideline 2.3.2?
Fix the listing, then reply. Metadata issues can often be fixed on the product page without a new build. Change the fields, then reply listing exactly what changed. This is how the guideline is usually resolved, not a prediction for your app.
How should I reply to App Review about Guideline 2.3.2?
Reply in App Store Connect. Thank the reviewer and name Guideline 2.3.2, 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 2.3.2?
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: 2.3 accurate metadata · 3.1.1 in-app purchase
Source: Apple's App Review Guidelines, section 2.3.2, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.