Guideline 2.3 rejection: Accurate Metadata
What it means, why it happens, and how developers get through it.
Subject line you may see: Guideline 2.3 - Performance - Accurate Metadata
Common real causes
- Screenshots show only splash, login, or marketing art (2.3.3)
- Competitor names, prices, or 'free' in name or keywords (2.3.7)
- 'for Kids' outside the Kids Category (2.3.8)
- Paid features not marked as paid (2.3.2)
How to fix it
- Show the app in use in screenshots
- Remove other brands, prices, and filler from name, subtitle, keywords
- Say clearly which features need a purchase
- Often a metadata fix and a reply, with no new build
What to put in your reply
Thank them and name Guideline 2.3. 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 2.3 is in the Rescue Kit.
Real cases: others who got 2.3
No public cases logged yet.
Questions developers ask about 2.3
What does a Guideline 2.3 rejection mean?
Something in your listing does not match the app or breaks a metadata rule.
Why do apps get rejected under Guideline 2.3?
The most common real causes: screenshots show only splash, login, or marketing art (2.3.3); competitor names, prices, or 'free' in name or keywords (2.3.7); 'for Kids' outside the Kids Category (2.3.8); paid features not marked as paid (2.3.2).
How do I fix a Guideline 2.3 rejection?
1. Show the app in use in screenshots. 2. Remove other brands, prices, and filler from name, subtitle, keywords. 3. Say clearly which features need a purchase. 4. Often a metadata fix and a reply, with no new build.
Do I need a new build for Guideline 2.3?
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?
Reply in App Store Connect. Thank the reviewer and name Guideline 2.3, 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?
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
Source: Apple's App Review Guidelines, section 2.3, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.