Rejection guides / Guideline 2.3: Accurate Metadata

Updated November 2026 · Appflight

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.

Explain my rejection

The parts of 2.3 that come up most

Likely causes

How to fix it

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.

Explain my rejection

Related guides

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)