Guideline4.3
Spam
4.3 is Apple grouping your submission with something they have already seen. The useful question is not “what is spam?” It is “what did they think you duplicated?”
§ 01What this rejection usually means
- The rejection is about similarity — binary, metadata, concept, or a pattern on the account — not about crash quality.
- You can receive 4.3 with only one live app. History, templates, and leftover identifiers are enough.
- The first fork in the road is Apple’s wording: similar binary, similar metadata, or similar concept.
§ 02Common causes
- Template, white-label, or purchased source that other developers already submitted.
- Several apps from one account that share a codebase or screenshots.
- Old bundle IDs, URL schemes, App Groups, or Firebase files left in a “new” project.
- Metadata or icon that looks like a known category clone.
- A classifier false positive on an original app with a common structure.
§ 03How to diagnose your case
- Read the sentence Apple wrote. Binary, metadata, and concept point to different checklists.
- Answer the tree: multiple apps, template source, then account history.
- Do not create a new bundle ID until you know what you are isolating.
§ 044.3 diagnosis tree
Have you submitted multiple similar apps from this account?
- Yes
Treat this as a portfolio overlap first. Compare the apps’ binaries, metadata, and positioning. Apple often wants consolidation, not another resubmit.
- No
Did you start from purchased, template, or white-label source?
- Yes
Audit the shared code, assets, bundle leftovers, and the vendor’s other App Store listings before you argue uniqueness.
- No
Does this developer account have related submission history — including deleted apps?
- Yes
Review old bundle IDs, team members, and previously rejected packages. History is enough to trip 4.3 even when you only have one live app.
- No
Inspect leftover identifiers, metadata, screenshots, and UI chrome. A single original app can still look like a repeat to the classifier.
- Yes
- Yes
§ 05What to inspect in your project
Checklist
- Bundle ID, extension IDs, App Groups, Keychain groups, URL schemes
- Associated Domains, push entitlements, Firebase / Google / Facebook config files
- Old product names in strings, asset names, and scheme URLs
- Icon, screenshots, subtitle, keywords, and description vs. known clones
- Developer account: deleted apps, other team members, prior 4.3s
§ 06What not to do
Do not
- Do not mint a new bundle ID as the first move.
- Do not move the same binary to another developer account.
- Do not only change the icon and name.
- Do not resubmit unchanged.
- Do not open with an appeal that accuses the reviewer of incompetence.
§ 07Questions people ask next
- I only have one app. Can I still get 4.3?
- Yes. Template code, leftover identifiers, and account history are enough. See the no-duplicate-apps page.
- Should I appeal Guideline 4.3 immediately?
- No. Appeal after you have a written diagnosis and, if needed, a reply that was ignored. Jumping to appeal with no evidence wastes the one serious review you get.