Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Apple rejected my app because of the screenshots or the store listing

Short answer

Apple's guideline 2.3 requires the listing to reflect the app accurately. Screenshots must show the app in use, not just a login or splash screen. Names and keywords cannot include prices or other apps' names, and the listing must not show other platforms. Fix the listing in App Store Connect, answer the reviewer, and resubmit.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Apple's message mentions guideline 2.3, metadata or screenshots.
  • The rejection says my screenshots do not show the app in use.
  • Apple says my app name or keywords break the rules.
  • A screenshot mentions Android, a price or a competitor.
  • App Store Connect will not accept my screenshot files.

Why does this happen?

  1. Screenshots must show the real app

    Guideline 2.3.3 says screenshots should show the app in use, not just title art, a login page or a splash screen. Overlays are allowed to demonstrate input, for example a touch point.

  2. The listing promises what the app does not do

    Metadata, including privacy information, description, screenshots and previews, must reflect the app's core experience and be kept up to date with each version. Marketing for features the app does not offer, or a false price, can get the app removed.

  3. Name, subtitle and keywords break the rules

    Guideline 2.3.7 asks for a unique name and keywords that describe the app. Names are limited to 30 characters. Trademarked terms, popular app names, prices and irrelevant phrases do not belong in them, and subtitles must not reference other apps or make unverifiable claims.

  4. Other platforms and sample data appear in the images

    Metadata should focus on Apple platforms and must not include names, icons or imagery of other mobile platforms or alternative app marketplaces. You must also have the rights to everything shown, and use fictional account information, not a real person's data.

  5. The files themselves are wrong

    Apple requires at least one screenshot, accepts up to ten per device size in jpeg, jpg or png, and says images cannot have an alpha channel or transparency. At least one screenshot is needed for the iPhone with Dynamic Island size, and the 13-inch iPad size if the app supports iPad.

What can I do about it today?

  1. Read the rejection message in fullNote the guideline number and the exact sentence. Reply only to what it says.
  2. Compare each screenshot with the guidelineDoes each image show the app being used? Does anything mention another platform, a price, an award or a real person?
  3. Check the name, subtitle and keywordsRemove prices, competitor names and anything that is not true of your app today.
  4. Describe new features in the Notes for ReviewApple says new features and changes must be described specifically there, and that generic descriptions are rejected.
  5. Make the screenshots from the current versionOld screens from a design mock-up cause mismatches. Use real captures with fictional sample data.
  6. Do not argue by repeating the same submissionFix what was named, then resubmit. If you disagree with a decision, Apple offers an appeal to the App Review Board.

When should I bring someone in?

  • The message is vague or you have been rejected for the same reason more than once.
  • You need new screenshots made from the real app in several sizes and languages.
  • The rejection is for a reason other than metadata, such as 4.3 spam or privacy.

How do I handle it?

  1. Match each point to the guideline textI read the message against Apple's guideline wording and make a short list of exactly what must change.
  2. Rebuild the listing assets from the real appI produce screenshots from the current build in the required sizes, with fictional data, and check file types and transparency.
  3. Clean the textName, subtitle, keywords, description and release notes are checked for prices, other platforms and untrue claims.
  4. Write a clear reply to the reviewerA short, factual reply says what was changed. If review notes need test logins or steps, I add them.
  5. Keep a pre-submission checklistThe same points are checked before each new release, so the next one does not bounce for the same reason.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can I use a designer's mock-up screenshots?

Apple's guideline says screenshots should show the app in use, not just title art, a login page or a splash screen. I would use real captures from the current version.

Do I need screenshots for every device?

Apple says that if your interface is consistent across sizes and languages you only need the highest required resolution, and it scales it down. Required sizes depend on which devices the app supports.

Can I mention that the app is also on Android?

Apple's guideline 2.3.10 says to focus metadata on Apple platforms and not include other mobile platforms' names, icons or imagery.

Is a metadata rejection a sign my app is bad?

No. It concerns the listing, and the guidelines say listing and app must agree.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.