App Store 2.3 rejection: Accurate store metadata
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad apps whose listing, screenshots, privacy information, or release details don't accurately describe the app.
Apple found a mismatch between the app and what you say about it. Under 2.3, metadata means the information around the app: its description, images, previews, privacy answers, and other store fields. These need to represent the version being reviewed.
Compare the listing with a fresh installation
Keep the submitted build and App Store Connect open together. Follow each advertised feature, compare screenshots, and check the price or paid access a user encounters. We’d include every localization; an old translation can keep a removed claim alive.
Use the numbered rules below to locate the specific problem. Screenshot content belongs under 2.3.3, keywords under 2.3.7, and pre-orders under 2.3.11.
Correct the mismatch at its source
Update inaccurate metadata or implement the missing feature before claiming it. If a screen is correct only for a particular account or region, explain how the reviewer can reach it.
Verify the saved store fields, images, and build together. Reply with the exact field or behavior changed. Some metadata corrections won’t need a new binary; follow the submission status and Apple’s instructions before rebuilding.
Messages this guide can help with
App Store 2.3 rejection; app store 2.3 denial; Guideline 2.3; Accurate store metadata
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Apple App Review guideline 2.3 Checked 22 September 2026