Rejection decoder › Guideline 2.3
Guideline 2.3 rejection: Accurate Metadata
Guideline 2.3 is about your App Store listing, not your code. Something in the name, subtitle, description, screenshots, preview or keywords does not match what the app actually does. Many 2.3 findings are fixed in App Store Connect without a new build.
Apple decides. This page is our own reading of the App Review Guidelines as of September 2026, not Apple's wording, and following it does not guarantee approval. The current text at developer.apple.com is the authority.
What Apple's message says
Apple usually cites a sub-guideline, and that number is the useful part. Paraphrased:
- 2.3 / 2.3.1: the description promises features the reviewer could not find, or the app contains features the listing does not mention.
- 2.3.3: screenshots do not show the app in use; they are mostly title art, a splash screen, a login screen or marketing mockups.
- 2.3.7: the name, subtitle or keywords are stuffed with search terms, use another company's brand, or claim something the app is not.
- 2.3.10: the app or listing mentions another platform, such as Android, Google Play, or "also on the web".
The message often includes a screenshot of the part Apple objected to. Look at it before you edit anything.
Why AI-built apps hit it
AI builders make it quick to produce a marketing site and an app at the same time, and the listing often gets copied from the site:
- The description lists roadmap features that the build does not have yet.
- Screenshots come from the landing page, with device frames around marketing art, or show only the sign-in screen.
- iPad screenshots are stretched iPhone captures, or there are none even though the app runs on iPad.
- A footer copied from the web app says "Get it on Google Play", or help text says "on Android, tap...".
- The name tries to rank for everything: "Planner - Budget, Money, Expense Tracker".
How to fix it, step by step
- Find the exact sub-guideline in the full message and fix only what it names. A broad rewrite can introduce a new problem.
- Description: describe only what the submitted build does today. Move future features out.
- Screenshots: capture the real app with realistic sample data. Upload at least the currently required iPhone size (6.9-inch at the time of writing) and the 13-inch iPad size if the app runs on iPad. Put the main feature in the first two. Captions are fine; the app must be the main content.
- Name and keywords: keep the name short and distinct (30 characters maximum), move descriptive words to the subtitle, and remove competitor or famous brand names from name, subtitle and keywords.
- Other platforms: search the app, description, What's New and screenshots for "Android", "Google", "Play Store" and "Chrome". Remove them, or hide them on iOS only.
- Decide whether a build is needed. If the problem was only in the listing, edit it and reply. If the words or placeholders were inside the app, upload a new build.
What to reply in the Resolution Center
Fill in the brackets and delete anything you did not do. Name the specific field you changed. If you also changed the build, give the new version and build number.
Hello, Thank you. Regarding Guideline 2.3.[x]: we updated the [description / screenshots / name / keywords] so it matches the app. Specifically, [what changed, e.g. "the screenshots now show the booking and history screens in use" or "we removed references to other platforms from the description"]. [If no new build: "No binary change was needed; the listing has been updated."] Best regards, [Your name]
Related guidelines
- Guideline 2.1: App completeness and Information Needed if the reviewer could not find a feature because it was broken rather than missing.
- Guideline 4.2: Minimum functionality if the screenshots reveal the app is mostly a website.
- Guideline 4.3: Spam if the listing looks like a copy of another app.
Questions
Do I need a new build to fix a Guideline 2.3 rejection?
Often not. If the problem is only in the name, description, keywords or screenshots, edit them in App Store Connect and reply in the Resolution Center. If the problem text or placeholder is inside the app, you need a new build.
Can App Store screenshots have captions and backgrounds?
Generally yes, as long as the real app in use is the main content. Screenshots that are mostly title art, a splash screen or a login screen are a common reason for a 2.3.3 rejection.
Why was I rejected for mentioning Android?
Guideline 2.3.10 does not allow references to other mobile platforms in the app or its metadata. Search your app, description and screenshots for Android, Google Play and similar terms, including text copied from a web version.
Stuck on this rejection?
Paste the full message into the free rejection decoder to see every cited guideline explained, with a reply draft. It runs in your browser and nothing is uploaded.
Or order a rejection fix, $99: we read the full message, find the cause, fix it in your project, upload a new build and draft the reply for your approval. Target turnaround 72 hours from access. Apple still makes the final decision, and its review time is separate.