Skip to content
Get a quote

App Store rejectionGuideline 4.3(a) - Design - Spam

App Review decided your app is too close to another app: one of yours, or apps from other developers. Unlike most rejections, this one is rarely a bug. Here’s what Apple’s rule says and what usually has to change.

Short answer

A 4.3 rejection means Apple sees your app as a copy: several near-identical apps under different Bundle IDs (4.3(a)), or an app indistinguishable from what’s already widely available (4.3(b)). The fix is usually a product change, such as merging the copies into one app, or making the app meaningfully different, not a code fix.

The two parts of 4.3, and what to change

  1. 01

    Several copies of the same app

    “Don’t create multiple Bundle IDs of the same app” Apple, Guideline 4.3(a)

    White-label apps, one app per client, city or location, and apps built from the same template as other developers’ apps all fall here. Developers on Apple’s forums report the message says the app shares a similar binary, metadata or concept with other apps. Apple’s 4.3(a) suggests one app with the variations provided through in-app purchase. For apps built for clients from a template, Guideline 4.2.6 (under Minimum Functionality) says they’re rejected unless the provider of the app’s content submits them, and names one app that hosts every client’s content, a “picker” model, as another acceptable option.

  2. 02

    An app too close to what’s already there

    “Don’t submit apps that are indistinguishable from what's already widely available.” Apple, Guideline 4.3(b)

    Apple gives examples of kinds of apps, such as dating, flashlight, wallpaper and simple timer apps, that are so well established it won’t accept new ones unless they offer a meaningfully different or improved experience. Developers report that changing the colors, name or icon rarely counts. What does is a feature or audience the existing apps don’t serve, shown clearly in the screenshots and the review notes.

  3. 03

    Explaining it in your reply or appeal

    If the app really is different, say how in your reply in App Store Connect: who it’s for, what it does that similar apps don’t, and whether it’s one app per business or one app for many. Developers report that renaming or restyling alone rarely changes the outcome, so lead with the product difference.

Checked against the vendor’s docs on : Apple: App Review Guidelines, 4.3 Spam (last updated October 16, 2026); Apple: App Review Guidelines, 4.2.6 (template and app generation services); Apple: App Review (replying and appeals); Apple Developer Forums: Guideline 4.3(a) rejection threads.

Rather hand it over?

Start with a paid consultation to agree what to change, then get a written quote with a fixed price.

Related: App Store Guideline 2.1 · App Store Guideline 5.1.1

Questions

More on this rejection

Should I reply to App Review or appeal?

Reply first. Apple says you can correspond with App Review in App Store Connect to resolve the issues before resubmitting, which is the place for a demo account, a screen recording or an explanation. Appeal to the App Review Board only if you believe App Review misunderstood the app or treated you unfairly. Apple allows one appeal per rejected submission and asks for specific reasons the app complies.

I build apps for clients from one codebase. Is that allowed?

Sharing a codebase isn’t what 4.3(a) names; submitting many near-identical apps is. Guideline 4.2.6 says template apps are rejected unless the provider of the app’s content submits them, and names one app that hosts every client’s content, a “picker” model, as another acceptable option.

Will changing the icon, name and colors get it approved?

Rarely. Developers report that redesigns and renames alone don’t change a 4.3 decision. Apple’s wording is about the app being indistinguishable, so the change has to be in what the app does or who it serves.

Can you help with a 4.3 rejection?

Usually this is a product decision before it’s any code, so it starts with a paid consultation to look at the rejection and the app and agree what to change. If it needs building, such as merging several apps into one, you get a written quote with a fixed price.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; we reply by email, usually within one business day.

Describe your problem All fixes