Ship Desk

Rejection decoder › Guideline 2.3.3 / 2.3.7

Guideline 2.3.3 and 2.3.7: screenshots, name and keywords

These two sub-guidelines are the most specific parts of 2.3. 2.3.3 is about screenshots that do not show the app in use. 2.3.7 is about a name, subtitle or keyword list that does not describe the app honestly. Both are usually 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

Paraphrased:

The general 2.3 page covers the other sub-guidelines, such as descriptions that promise missing features and references to other platforms.

Why AI-built apps hit it

The listing for an AI-built app is usually made in the same afternoon as the landing page:

How to fix it, step by step

  1. Capture from the real build. Run the app in the iOS Simulator on the largest iPhone and, if the app supports iPad, the largest iPad. Use xcrun simctl io booted screenshot shot.png or File > Save Screen. Use realistic sample data, not "Lorem ipsum" or "Test user".
  2. Use the required sizes. At the time of writing, App Store Connect asks for a 6.9-inch iPhone set (for example 1320 x 2868 portrait) and, for iPad apps, a 13-inch set (for example 2064 x 2752). Check the current screenshot specifications before uploading.
  3. Order for the reviewer and the buyer. Screenshot one shows the main thing the app does. Skip the login screen.
  4. Captions are fine; the app must be the main content. A short caption above a real screen works. A slide that is mostly artwork does not.
  5. Rewrite the name: a short distinct name, 30 characters maximum, with descriptive words moved to the 30-character subtitle.
  6. Rewrite the keywords (100 characters, comma-separated): no repeats of words already in the name, no competitor or brand names, no "free", "best" or "#1".
  7. If the app does not support iPad well, consider turning iPad support off in the build rather than submitting weak iPad screenshots. That change needs a new build.

What to reply in the Resolution Center

Fill in the brackets and delete anything you did not do. If you only edited the listing, say so, so the reviewer knows not to wait for a build.

Hello,

Thank you. Regarding Guideline 2.3.[3 / 7]: we replaced the [iPhone / iPad] screenshots with captures of the app in use, showing [main screens, e.g. "the daily check-in and progress screens"]. [We changed the app name to "[name]", moved descriptive terms to the subtitle, and removed third-party names from the keywords.]

No binary change was needed; the listing has been updated.

Best regards,
[Your name]

Related guidelines

Questions

Can I make App Store screenshots from my website?

Screenshots should show the iOS app in use, as it looks on the device size you upload them for. Desktop captures of a website placed in a phone frame are a common 2.3.3 finding. Capture from the Simulator or a device running the submitted build.

Do I need iPad screenshots?

If the build supports iPad, App Store Connect asks for an iPad set, and it should show the app as it runs on iPad. Stretched iPhone captures are a common rejection. If the app is not designed for iPad, removing iPad support in the build is an option.

Can I put competitor names in my keywords?

No. Guideline 2.3.7 does not allow trademarked terms, other apps' names or unrelated phrases in the name, subtitle or keywords. Use words that describe what your app does.

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.