How to Fix App Store Guideline 2.3 Metadata Rejection
Align App Store screenshots, descriptions, claims, age rating, and review notes with the submitted build after a Guideline 2.3 rejection.
What this rejection usually means
A 2.3 rejection means the product page or review information does not accurately represent the submitted app. Common triggers include outdated screenshots, inaccessible features, irrelevant keywords, unsupported claims, platform references, missing purchase context, or generic Notes for Review.
Likely rejection signals
- Screenshots show a feature absent from the reviewed build
- Description promises unsupported results or capabilities
- Keywords, title, or subtitle include irrelevant or trademarked terms
- Review notes omit a non-obvious feature or test path
Recovery plan
- Audit every screenshot, preview, title, subtitle, description claim, keyword, age-rating answer, and review note against the current build.
- Remove future features, unsupported performance claims, prices in restricted metadata fields, and irrelevant platform references.
- Replace screenshots with captures from the submitted version and fictional account data.
- Make non-obvious features and purchases accessible and explain them specifically in Notes for Review.
- Repeat the audit across all localizations, not only the default language.
Evidence to prepare
- Claim-to-screen mapping for every material statement
- Current-build screenshots for every localization
- Accurate age-rating and privacy answers
- Numbered reviewer path for non-obvious functionality
Appeal or fix first?
Clarify when the metadata is accurate but the reviewer overlooked a feature that is present and accessible. Point to the exact screen and path.
Fix first when any claim, screenshot, keyword, preview, or localization does not match the submitted binary.
Reviewer response framework
Your response should be factual, short, and limited to the submitted build. Cover these points:
- Identify the exact metadata fields changed.
- Confirm that screenshots and claims match the submitted build.
- Give a direct path to the relevant feature.
- Do not add marketing language to the reviewer reply.
Frequently asked questions
Do metadata changes require a new binary?
Not always. If the issue is limited to editable metadata, you may be able to correct it without changing the binary. A product mismatch still requires a product or build change.
Should screenshots show real customer data?
No. Apple recommends fictional account information in screenshots and previews.
Need a rejection-specific plan?
Start with the free diagnosis. The $29 Fix Pack adds the prioritized remediation plan, evidence checklist, reviewer-ready reply, and preflight.
Source: Apple App Review Guidelines — 2.3 Accurate Metadata. Platform policies change. Verify the official rule before submitting. Resubmit AI provides technical and editorial decision support, not an approval guarantee or legal advice.