Guideline2.3
Accurate Metadata
2.3 is a listing problem. The store page promises something the binary does not do, or the screenshots, name, or category mislead a reviewer about what they will open.
§ 01What this rejection usually means
- Apple compared the listing to the binary and found a mismatch.
- Screenshots from another product, mocked UI, or an iPad layout on an iPhone listing are frequent hits.
- This is one of the few rejections that often does not need a new binary.
§ 02Common causes
- Screenshots include features that are not in this build or not on this platform.
- App name or subtitle implies a capability you do not ship (AI, banking, kids, medical).
- Promotional text or description contradicts in-app copy.
- Preview video shows a different theme, language, or paywall.
- Category does not match the actual use.
§ 03How to diagnose your case
- Open the rejected version’s App Store listing next to the binary and walk every screenshot.
- Search the description for claims you cannot demonstrate in under two minutes.
- If the binary is fine and only the listing is wrong, stay on metadata. Do not rebuild.
§ 05What to inspect in your project
Checklist
- Every screenshot is from the submitted binary, same OS and device class
- Name, subtitle, keywords, and promotional text
- In-app purchase display names vs. store copy
- App preview video vs. first-run experience
- Age rating and category vs. actual content
§ 06What not to do
Do not
- Do not replace screenshots with marketing renders that the app cannot reproduce.
- Do not change the binary just to match a slogan. Change the slogan.
- Do not bury the mismatch in a long appeal.
§ 07Questions people ask next
- Can I fix 2.3 without a new build?
- Usually yes. Accurate metadata is a store-page problem. Resubmit after you correct screenshots, copy, or category.