Screenshots show actual current app UI

Screenshots that show a more polished UI than the shipping build, marketing renders dressed up as device captures, or features absent from the codebase trigger App Store rejections under Guideline 2.3.3 (Accurate Metadata). Users who install based on inaccurate screenshots leave 1-star reviews within the first session, tanking conversion and store ranking. Missing required device sizes (6.5 inch iPhone, 12.9 inch iPad) block submission outright before review even begins.

Capture screenshots directly from a device or simulator for every required size, then commit them to fastlane/screenshots/<locale>/ so review state is reproducible. Automate capture with fastlane snapshot for iOS and fastlane screengrab for Android so screenshots regenerate from the current build on every submission rather than drifting out of sync.

bundle exec fastlane snapshot
bundle exec fastlane screengrab

• ID: screenshots-actual-ui
• Severity: high
• What to look for: Examine screenshot files in fastlane/screenshots/, store-assets/screenshots/, assets/screenshots/, or any directory containing .png or .jpg files with device-sized dimensions (standard screenshot sizes: 1284×2778 for iPhone 6.5", 2048×2732 for iPad, 1080×1920 for Android). Check for: (a) screenshots that appear to be from a different, more polished version than the current codebase (e.g., screenshots show a feature not present in any source file), (b) screenshots with placeholder content (lorem ipsum visible in the screenshot filename metadata or alt text), (c) no screenshots at all in any standard location, (d) screenshots that appear to be renders or mockups rather than actual device captures (filename patterns like mockup_, render_, marketing_ suggest marketing assets rather than device screenshots), (e) for Expo, check app.json or eas.json for any screenshots configuration. Also verify screenshot filenames include device type indicators — reviewers need screenshots for specific required device sizes. For iOS: at minimum 6.5" iPhone (1284×2778 or 1242×2688) and 12.9" iPad if the app supports iPad. For Android: phone screenshots are required; tablet screenshots recommended. Count every screenshot in the metadata directory and enumerate each. For each screenshot, classify as matching current UI or outdated/misleading.
• Pass criteria: Screenshots are present, appear to show actual app UI (not renders or templates), cover required device sizes for the target platform, and the UI visible in screenshots matches features present in the codebase. Report even on pass: "X screenshots reviewed. All X match the current UI version." At least 1 implementation must be confirmed.
• Fail criteria: No screenshots found anywhere in the repository; screenshots appear to be mockups or marketing renders; screenshots show features absent from the codebase; required device sizes appear to be missing. Do NOT pass if screenshots show a materially different UI than the current app version — this is a common rejection reason.
• Skip (N/A) when: Screenshots are managed entirely outside the repository (e.g., uploaded directly through App Store Connect or Play Console with no local copies committed). This is common — skip rather than fail if no screenshot files are present at all.
• Cross-reference: The preview-video check in Review & Submission verifies any video assets match the current UI alongside the screenshots validated here.
• Detail on fail: "No screenshot files found in any standard location — screenshots must be present in App Store Connect before submission" or "Screenshots appear to be marketing mockups (filenames: 'marketing-render-01.png') rather than actual device captures".
• Remediation: App Store Connect rejects submissions that lack the required screenshot sizes. Inaccurate screenshots that don't represent the actual app can trigger rejection after review.
  1. Take screenshots directly from a device or simulator for each required size
  2. Required iOS sizes: 6.5" iPhone (1284×2778 or 1242×2688) — required; 12.9" iPad (2048×2732) — required if iPad supported
  3. Required Android sizes: Phone screenshots — required; Tablet screenshots — strongly recommended
  4. Use real device screenshots or Xcode Simulator / Android Studio screenshots — not marketing mockups
  5. Screenshots can include device frames and text overlays, but the underlying UI must be real
  6. Consider using fastlane snapshot (iOS) or fastlane screengrab (Android) to automate screenshot capture Store screenshots in fastlane/screenshots/ or src/store-metadata/screenshots/. Regenerate from current builds using fastlane snapshot or manual capture.