ReviewAhead

No, and nothing can. App Review evaluates a running app, its content and its metadata, none of which a project scan can see. What ReviewAhead does is find the preventable problems that are visible in your project, before Apple is the one telling you about them.

Not to scan. The button takes you to sign-in first, and that page has a link straight past it to the scanner. An account keeps your reports and history across devices, and is required for scanning straight from a GitHub repository.

The upload and the extracted source are deleted the moment the scan finishes, on the failure path as well as the successful one. What is kept is the report: the score, the findings and short evidence excerpts, redacted where they matched credential-shaped text. Whole files are never stored.

No. There is no code path that compiles your project, runs a build phase or script, installs a dependency, or contacts a URL found inside your files. Everything is read as text, and dependency manifests like Package.swift and Podfile are parsed, never evaluated.

The folder that holds your .xcodeproj, a .zip of it, an .ipa, or a GitHub repository you have shared with ReviewAhead. Archives are validated before anything is extracted. An archive holding only a Swift package gets dependency analysis but no target, configuration or Info.plist checks, because there is no Xcode project to read. An .ipa is read as a build: the shipped Info.plist, privacy manifests, embedded frameworks and the entitlements it was signed with, and nothing that needs source code, because a build carries none.

If you link the app, yes. The age rating questionnaire, screenshot uploads, release notes, purchase states and review details are then read from your own listing instead of being asked as questions, and that read becomes the evidence. Without a linked app those rules state the requirement and work out which parts of it apply to your build.

AI can explain an App Store rule. ReviewAhead checks whether your project actually satisfies it: the same thirty-eight versioned rules against your parsed build settings, Info.plist, entitlements and dependency graph, with the file and line behind every finding. There is AI review here too, part of the unlimited plan and switched off until you turn it on from the scan screen, and even then it can only suggest wording and explain a finding: it can never add a finding, remove one, or change a severity.

Every scan gives you the readiness score, the verdict, the count of findings at every severity and your three most severe findings in full. Unlocking that report, $2.99 once, adds every remaining finding with its evidence and fix, plus a PDF export. Unlimited is $4.99 a month and covers every scan and report.

You fix what it found and run it again. Findings are matched by rule, target and evidence key, so a fix still counts as fixed when the file moved, and the second report shows what you cleared and what is new.