Guideline 2.3 — Accurate Metadata
Your listing promises something the app does not show. Apple treats the product page as part of the product: screenshots must be real screens, the description must describe what ships today, and nothing may point at Android.
What the rejection usually says
Your app screenshots do not sufficiently reflect your app in use.
Your app description contains references to other mobile platforms.
Your app name or subtitle includes keywords that are not relevant.
Wording varies between reviewers; the substance does not.
Why it gets triggered
- Marketing screenshots that show a concept, a device mock-up filled with stock imagery, or features that are not in this build.
- The description mentions Android, Google Play, or a price promotion.
- Keyword stuffing in the name or subtitle, or naming competitors.
- A future feature described in the present tense.
How to fix it
1.Show real screens
Every screenshot must contain a genuine screen from this build. Captions and backgrounds around it are fine — the screen itself cannot be invented.
2.Strip cross-platform references
Search the description, subtitle, promotional text and what-is-new for Android, Google Play, Windows and any other store.
3.Keep the name honest
Name and subtitle describe the app, they are not keyword fields. The keyword field is separate and invisible to users.
4.Match the build
If a feature slipped, cut it from the description now and add it back with the release that ships it.
A reply you can adapt
Short, specific, and stating what changed — reviewers read hundreds of these.
Thanks for flagging this. We have replaced the screenshots with captures from the current build, removed the reference to other platforms from the description, and rewritten the subtitle to describe the app rather than list keywords.
AppSubmit does this for your app, specifically
Paste the rejection and the decoder reads it against your actual listing, build and release history — then writes the fix plan and drafts the reply. It also watches your submissions, so the next rejection reaches you as a notification rather than a surprise.
Decode a rejection free