Template / starter-kit fingerprint
Check PB-39 · App Store Review Guideline 4.3 · Review warning · verified 2026-09-16
Why App Review rejects under Guideline 4.3
4.3 is a judgment call, so there is no checklist that guarantees a pass. What reliably triggers it is mechanical though: placeholder bundle identifiers, starter-kit strings left in the build, generic names and icons, screenshots that look like every other app in the category. Remove those signals, make the first screen obviously yours, and if you are still rejected reply in the Resolution Center with three concrete sentences about what is different. Reviewers do reverse 4.3 when you argue the difference; they do not when you resubmit silently.
How to fix it
Apps that look like an unmodified template get flagged under 4.3 (Spam) even when the code is fine. Use your own reverse-DNS bundle id (com.yourbrand.appname), remove starter-kit markers from the project name and bundle, and make the first screen clearly yours. If you are rejected under 4.3, reply in App Store Connect with what makes the app distinct.
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-39 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.