Rejection guides / Guideline 2.3: Accurate Metadata
Guideline 2.3 - Performance - Accurate Metadata, explained
Your App Store listing has to match what the app actually does. 2.3 rejections are about the listing, so they can often be fixed without touching code.
"Customers should know what they're getting when they download or buy your app, so make sure all your app metadata, including privacy information, your app description, screenshots, and previews accurately reflect the app's core experience and remember to keep them up-to-date with new versions."App Review Guideline 2.3, Apple
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
The parts of 2.3 that come up most
- 2.3.3 Screenshots: they should show the app in use, not only title art, a login page or a splash screen.
- 2.3.7 Name and keywords: app names are limited to 30 characters, and metadata shouldn't be packed with trademarked terms, popular app names, pricing or other irrelevant phrases.
- 2.3.10 Other platforms: no names, icons or imagery of other mobile platforms or alternative app marketplaces in the app or its metadata, unless there's approved interactive functionality.
- 2.3.1 Hidden or misleading features: new features must be described specifically in the Notes for Review, and the app can't promote content or services it doesn't offer.
- 2.3.2 In-app purchases: the description, screenshots and previews should make clear which items need an extra purchase.
Likely causes
- Screenshots are marketing art or a login screen rather than the app in use.
- The description or screenshots promise a feature the reviewer couldn't find in the build.
- A competitor's name, another app's name or a price appears in the name, subtitle or keywords.
- A screenshot shows an Android phone, a Google Play badge or text like "also on Android".
- The listing still describes the old version after a major change.
How to fix it
- Replace screenshots with real screens from the current build. Text and frames around them are fine.
- Remove any claim the reviewer can't verify in the app, or make the feature reachable and explain where it is in the review notes.
- Clean the name, subtitle and keywords of other brands, app names and prices.
- Remove references to other platforms from screenshots, descriptions and the app itself.
- Metadata changes don't need a new build in most cases. Edit the listing and reply in App Store Connect.
Common questions
- Do I need a new build to fix a 2.3 rejection?
- Usually not. Most 2.3 issues are in the listing, which you can edit in App Store Connect. If the problem is inside the app, such as a reference to another platform in the UI, you need a new build.
- Can I mention that the app also works on the web?
- 2.3.10 is about other mobile platforms and alternative app marketplaces. Keep the listing focused on the app itself and its experience, and avoid naming other mobile platforms.
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
Related guides
- Guideline 2.1: App Completeness (crashes, bugs, placeholders)
- Guideline 4.3: Spam
- Checklist: Before you submit to App Review
Apple decides every review. These guides explain what the guidelines say and what usually helps. They can't promise an approval.
Sources: App Review Guidelines (Apple)