Skip to content

App Store rejectionGuideline 2.3 - Performance - Accurate Metadata

The app may be fine, but App Review rejected what the App Store listing says or shows about it. The rejection message names the guideline. Here’s what each part of 2.3 means in Apple’s own words and what to change, or hand it over at a fixed price.

Short answer

Guideline 2.3 is about the listing, not the code: Apple wants the screenshots, previews, description and other metadata to match the app’s core experience. Common fixes are screenshots of the app in use rather than a splash or login screen, previews made only of screen captures, clear notes on what costs extra, and removing other platforms’ names and icons. Check which item the reviewer named, change it, then resubmit.

What the reviewer flagged, and the fix

  1. 01

    Screenshots don’t show the app in use

    “Screenshots should show the app in use, and not merely the title art, login page, or splash screen.” Apple, Guideline 2.3.3

    Replace title cards, login screens and splash screens with screens from the app doing its main job. Text and image overlays are allowed on top. Use made-up account details in them, not a real person’s data.

  2. 02

    The preview video isn’t a screen capture

    “previews may only use video screen captures of the app itself.” Apple, Guideline 2.3.4

    Rebuild the preview from recordings of the app itself. Narration and video or text overlays can explain what isn’t clear, but the footage itself should come from the app (stickers and iMessage extensions may show the Messages app).

  3. 03

    The listing promises something the app doesn’t do

    “make sure all your app metadata, including privacy information, your app description, screenshots, and previews accurately reflect the app’s core experience” Apple, Guideline 2.3

    Read the description, subtitle and screenshots as a new customer would, and remove or reword anything the reviewer couldn’t find in this build.

  4. 04

    The Notes for Review are too generic

    “All new features, functionality, and product changes must be described with specificity in the Notes for Review section of App Store Connect (generic descriptions will be rejected)” Apple, Guideline 2.3.1(a)

    When a version adds features or changes the product, list each change in the Notes for Review in App Store Connect, say where to find it, and make sure the reviewer can reach it. A line like "bug fixes and improvements" isn’t enough for a new feature.

  5. 05

    It isn’t clear what costs extra

    “make sure your app description, screenshots, and previews clearly indicate whether any featured items, levels, subscriptions, etc. require additional purchases.” Apple, Guideline 2.3.2

    If a screenshot or the description features something behind a subscription or in-app purchase, say so where it’s shown.

  6. 06

    Android or other platform names and icons appear

    “don’t include names, icons, or imagery of other mobile platforms or alternative app marketplaces in your app or metadata, unless there is specific, approved interactive functionality.” Apple, Guideline 2.3.10

    Look for a Google Play badge, an Android screenshot or "also on Android" text, in the listing and in the app, for example a screenshot taken on another platform. Remove them from the iOS build and its metadata.

  7. 07

    The name, subtitle or keywords are packed

    “Metadata such as app names, subtitles, screenshots, and previews should not include prices, terms, or descriptions that are not specific to the metadata type.” Apple, Guideline 2.3.7

    Keep the app name to 30 characters, and take prices, other apps’ names and trademarked terms out of the name, subtitle and keywords.

Checked against the vendor’s docs on : Apple: App Review Guidelines, 2.3 Accurate Metadata (last updated October 16, 2026); Apple: App Review (replying and appeals).

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Resubmit before Apple’s holiday slowdown

Pay for the Diagnosis and send the rejection and access to the app by (US Eastern). The Diagnosis is back by . Pay for the Fix that day and it arrives as a pull request by , in time to build and resubmit before .

In past years Apple said reviews may take longer around the holidays: December 20 to 26 in 2024 (opens in a new tab), December 22 to 27 in 2023 (opens in a new tab), December 23 to 27 in 2022 (opens in a new tab). Apple hasn’t posted its 2026 dates yet (checked ). Approval stays Apple’s decision.

Related: App Store Guideline 2.1 · App Store Guideline 4.2 · App Store optimization guide · App Store Guideline 3.1.1

Questions

More on this rejection

Should I reply to App Review or appeal?

Reply first. Apple says you can correspond with App Review in App Store Connect to resolve the issues before resubmitting, which is the place for a demo account, a screen recording or an explanation. Appeal to the App Review Board only if you believe App Review misunderstood the app or treated you unfairly. Apple allows one appeal per rejected submission and asks for specific reasons the app complies.

Does a 2.3 rejection need a new build?

Check which item the reviewer named. Items that only appear in the listing are edited in App Store Connect; anything shown inside the app, such as another platform’s name or icon, needs a new build.

What should the “What’s New” text say?

Apple asks for new features and product changes to be described clearly. Simple bug fixes, security updates and performance improvements may use a generic line, but more significant changes must be listed.

Can you fix it for me?

Yes, through the App Fix Ticket: you send the rejection message and access to the app, Simon writes a diagnosis of what App Review hit and how to fix it, then fixes the code so you can resubmit. Each step has a fixed price, paid upfront. Approval stays Apple’s decision; the ticket covers the fix.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; we reply by email, usually within one business day.