Guideline 4.3 (Spam): what it means and how to get approved
Last reviewed 18 October 2026
A 4.3 rejection is one of the hardest to read. It rarely says exactly what’s wrong, and resubmitting the same build gets the same answer. Here’s what Apple is usually reacting to, and what works.
Apple sees your app as a duplicate: one of several near-identical apps, or one more app of a kind the store already has plenty of. You fix it by making the app clearly different or by consolidating, not by tweaking the icon or screenshots.
What Apple is saying
Guideline 4.3 has two parts, and the rejection names one of them:
- 4.3(a), duplicate apps: the same app submitted under several bundle IDs, for example one per city, team, university or client. Apple’s suggestion is a single app, with the variations offered inside it.
- 4.3(b), crowded categories: apps indistinguishable from what’s already widely available. Apple names dating, flashlight, sound effect, wallpaper, simple timer and fortune-telling apps as categories where it only accepts a meaningfully different or improved experience.
“Don’t create multiple Bundle IDs of the same app”
Rejection messages often add that your app shares a similar binary, metadata or concept with other apps, with only minor differences.
The usual causes
- White-label apps: the same app re-skinned for each client and submitted from one developer account. Apps made from commercial templates or app builders also fall under Guideline 4.2.6 unless the owner of the content submits them.
- A bought template or clone script that other developers have already shipped.
- Several apps for variations of one product: one per location, team or brand.
- A crowded category where the app adds little that’s new.
- A removed app resubmitted under a new bundle ID or a new account.
- Generic metadata: a name, description and screenshots that look like other apps’.
How to fix it
- Read the exact sub-rule. 4.3(a) is about your own duplicates; 4.3(b) is about the category. The fix is different for each.
- If it’s white-label, change who submits. Each client publishes from its own Apple Developer organisation account with its own content, or you put every client inside one app where users choose their organisation. Apple calls this a “picker” model.
- If you have near-identical apps, merge them. One app with the locations, brands or content inside it, using in-app purchase for paid variations where it makes sense.
- If it’s a template, change what’s underneath. Rework the core flows and features so the app does something the template doesn’t. New colours and a new name aren’t enough.
- Show the difference in the first minute. Reviewers spend little time in each app. Put the feature that makes you different on the first screens, and point to it in the review notes.
- Rewrite the metadata. A specific name, a description that says who the app is for and what’s unique, and screenshots of your real screens.
- Reply to App Review before resubmitting. Explain clearly what’s unique, who owns the content and why it’s a separate app. See how to reply and when to appeal.
What doesn’t work
- Resubmitting the same build and hoping for a different reviewer. Apple says repeated rejections for the same guideline make review take longer.
- Changing only the icon, name or colours.
- Opening a new developer account to submit the same app. Apple warns that repeated submissions of this kind can lead to removal from the Apple Developer Program.
Questions founders ask
How long does it take to fix a 4.3 rejection?
If the fix is changing who submits the app or merging variants into one app, it can be days. If the app needs real changes to stand apart from a template, plan for a few weeks of work.
Can a white-label app be approved?
Yes, when each client publishes from its own developer account with its own content, or when all clients live inside one app.
Will a 4.3 rejection hurt my developer account?
One rejection doesn’t. Repeatedly submitting near-identical apps can lead to removal from the Apple Developer Program, so fix the cause before you resubmit.
More rejection guides
- Guideline 4.2 (Minimum Functionality)
- How to reply to a rejection, and when to appeal
- Guideline 2.1 (App Completeness)
- Guideline 3.1.1 (In-App Purchase) and 3.1.2 (Subscriptions)
- Guideline 5.1.1 (Data Collection and Storage)
- All App Store rejection guides
Based on Apple’s App Review Guidelines as last updated by Apple on 16 October 2026. Apple changes them from time to time, so check the current text on Apple’s developer site.