Version or build number missing/invalid
Check PB-25 · App Store Review Guideline 2.3 (metadata) · Likely rejection when present · verified 2026-09-16
Why App Review rejects under Guideline 2.3
2.3 rejections come from App Store Connect, not from the code: an app name that contains "beta" or "test", keywords stuffed with competitors' names, a description that mentions Android, screenshots that do not match the current build. Reviewers read the listing as a set of claims and test each one. The fix is editorial — rewrite the fields — but two of the checks can be caught from the binary too: placeholder wording in CFBundleDisplayName and localizations that do not match what you declared.
How to fix it
Enter a proper version (e.g. 1.0.0) and build number. Expo: app.json → expo.version and expo.ios.buildNumber.
How RejectProof detects it
The scan reads your .ipa in the browser (or locally with npx rejectproof): Info.plist, entitlements, the privacy manifest, embedded frameworks and the executable itself. Check PB-25 reports the exact evidence it found — the key, the symbol, the file or the URL — so you can confirm it in your own project before changing anything. Nothing is uploaded; only a small redacted summary is sent to build the report, and you see it first.