What problem does it solve? Apps are frequently rejected by Apple App Review for preventable configuration mistakes such as sub-1.0 version numbers, beta labels in the app name, staging endpoints, missing demo credentials, and forced-update gates that lock reviewers out of the submitted binary. ## Core Features & Use Cases - Configuration Scanning: Checks MARKETING_VERSION in project.pbxproj, CFBundleDisplayName in Info.plist, and hardcoded staging or localhost URLs in Swift source files. - Reviewer Access Validation: Verifies that demo credentials are documented when the app requires login, and flags forced-update gates that block access to the submitted build. - Prioritized Findings Report: Outputs findings grouped by severity (CRITICAL, HIGH, MEDIUM, LOW) with file paths, line numbers, and mapped App Review Guidelines 2.1 and 2.3. - Use Case: Before submitting an iOS app, run this check to catch a 0.9 marketing version, a staging API base URL, and missing review notes so you can fix them before Apple rejects the build. ## Quick Start Ask the assistant to run a review readiness check on your iOS project root before submitting to the App Store.