App Store RejectionGuideline 2.3.1 — Accurate Metadata

Your screenshots show a different app than what reviewers actually opened.

Guideline 2.3.1 means every screenshot, preview video, and word in your description must accurately represent the current version of your app — no aspirational features, no borrowed UI.

What Apple said

“We noticed that your app's screenshots and/or description do not accurately represent the app's current features and functionality. Specifically, the screenshots appear to display features or content that are not present in the reviewed build. Please update your metadata to accurately reflect the current version of your app.”

What this actually means

Apple reviewers open your app and compare it directly against your screenshots and description. If your screenshots show a polished onboarding flow that doesn't exist yet, show a dark mode you haven't shipped, or use stock-photo device mockups that obscure the actual UI, you'll get rejected. The description must also match — don't list features that are 'coming soon' as if they're already available.

What Apple needs to see

  • Screenshots taken directly from the current build of your app, showing real screens users will actually encounter
  • No features mentioned in the description that are not present and functional in the submitted binary
  • If you use device frames or marketing graphics over screenshots, the actual app UI must still be clearly visible and accurate
  • App name and subtitle must describe what the app actually does — no keyword stuffing or category misrepresentation
  1. 1Open your current app build and take fresh screenshots on the correct device sizes (6.9" and 6.5" iPhone at minimum) using Xcode Simulator or a physical device.
  2. 2Review every sentence in your App Store description and remove or rewrite any references to features, screens, or functionality not present in the current submitted version.
  3. 3If you use a tool like Previewed or AppMockUp to add device frames, re-export with the new screenshots so the UI inside the frame matches what reviewers will see.
  4. 4Read your app subtitle and keyword field and remove any terms that describe categories your app doesn't belong to or features you haven't built.
  5. 5Do a side-by-side comparison — open your App Store Connect listing and your actual app simultaneously — and verify every visual element matches before resubmitting.

While you're at it — Apple also requires these pages for every app.

Fix this rejection, then make sure you're covered on the compliance side too. Apple requires every app to link to a hosted Privacy Policy, Terms of Service, Support page, and Data Deletion page. No link means another rejection — just for a different reason.

Privacy Policy
Terms of Service
Support Page
Data Deletion Page
Marketing Page
Generate my compliance pages — $9

Common questions

Can I show 'ideal state' screenshots with sample data pre-populated?
Yes, showing the app with realistic sample data or a populated state is fine — that is standard practice. What you cannot do is show UI, features, or screens that do not exist in the submitted binary at all.
Is it okay to mention a feature is 'coming soon' in the description?
No. Apple's position is that metadata should describe the current version, not a roadmap. Save the roadmap for your website or release notes. Remove all 'coming soon' language before resubmitting.
My app got rejected for the title. What counts as a misleading title?
Titles that include category keywords ('Best Free VPN'), competitor names, or descriptors that exaggerate functionality ('AI-Powered' when there is no AI) are all flagged under 2.3.1. Keep the title to your actual brand name.

Ready to pass review?

Generate all your compliance pages in 60 seconds.

Get started — $9