Screenshots show actual current app UI
Why it matters
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.
Severity rationale
High because inaccurate or missing screenshots are a top-five App Store rejection cause and a documented 2.3.3 violation.
Remediation
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
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the App Store Metadata & Listing Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from app-store-metadata-listing·automated