Start with your own catalog: the most common 4.3 trigger is a developer's own near-identical siblings. Apple names the saturated categories itself — dating, flashlight, soundboard, wallpaper, timers, fortune telling — and apps in them start the review with the burden of proof on differentiation.
Got the actual message? Paste it into the free rejection decoder — it matches your rejection against documented store rules and returns the fix steps, the resubmission checklist, and a reply draft. Three free decodes, no account.
4.3 — Spam / Duplicate Apps
Apple sees your app as a duplicate — of your own other apps, of a template family, or of a saturated category (Apple names dating, flashlight, soundboard, wallpaper, timers, and fortune-telling type apps). Submitting multiple Bundle IDs of essentially the same app is a per-se violation.
Severity: blocker · Decoder confidence for this class: B (see the honesty note below)
The fix
- Audit your own developer catalog for sibling apps with overlapping content/functionality — this is the most common trigger.
- Consolidate near-duplicates into a single app (variants as content/in-app purchases inside one binary) and remove the redundant listings.
- If the app is genuinely distinct, document the differences concretely: unique content, unique features, different audience workflows.
- Do not resubmit the same app under a new Bundle ID — that compounds the violation and can escalate to account action.
Resubmission checklist
- Own catalog audited for duplicates
- Redundant listings consolidated or removed
- Differentiation documented in the reply
- No new Bundle ID for the same app
Reply draft
Hello App Review Team, Thank you for the feedback. We reviewed our catalog and [consolidated [APPS] into a single app / removed the overlapping listing(s)]. [OR: This app differs from others in the category in the following specific ways: [FEATURE/CONTENT DIFFERENCES].] We respectfully request re-review of build [X]. Thank you for your time. [NAME]
What the decoder can diagnose here: The likely comparison set: your own catalog first (Apple usually means your near-identical siblings), then the category. What it cannot: Exactly which apps Apple compared against — they rarely name them. The working fix is differentiation you can demonstrate feature-by-feature, or consolidation into one app with in-app variants.
Rule text: “Don't create multiple Bundle IDs of the same app... Also avoid piling on to a category that is already saturated; the App Store has enough fart, burp, flashlight, fortune telling, dating, drinking games, and Kama Sutra apps, etc. already.” — App Review Guidelines §4.3(a)/(b), retrieved 2026-10-23
Related guides
- Rejection decoder — paste your message, get the fix
- App Store Pre-Flight — the full check and $29 Founding pre-sale
- Google Play Pre-Flight — deadlines and declarations
- Guideline 4.2 — Minimum Functionality (and template apps)
Sources
- App Review Guidelines §4.3(a)/(b), retrieved 2026-10-23
Last updated October 23, 2026. Rules change; the retrieval dates above say when this page was last checked against the store's published text.
Decode your rejection — free
The decoder covers 41 documented rejection patterns across the App Store and Google Play, grounded in the stores' own published rules. Three free decodes; the $29 Pre-Flight Founding pre-sale unlocks unlimited decoding plus a full pre-flight check credit when the checker ships.
The decoder classifies and guides from the message you paste. It cannot see your app or your binary, and it never promises an approval outcome — that decision is always the store's.