Guideline 4.3(a) Design Spam: how to fix it, with 4.3(b) and 4.2.6 explained for template and AI apps (2026)

A Guideline 4.3(a) Design Spam rejection is one of the hardest App Review messages to act on, because it rarely says which app yours resembles. It hits template apps, white-label clients and AI-generated apps much more often than others. This guide separates 4.3(a) from 4.3(b) and 4.2.6, looks at how other developers got past the rejection, and gives you a reply template and a checklist to finish before you resubmit. For other rejection types, see the guideline-by-guideline rejection guide.

What does Guideline 4.3(a) Design Spam mean?

Guideline 4.3(a) means Apple thinks your submission is substantially the same app as one already submitted, either several bundle IDs of one app or a near-copy of someone else's. The fix is to consolidate the duplicates or make the core experience clearly different.

As of November 2026, the App Review Guidelines say: "Don't create multiple Bundle IDs of the same app (for example, submitting a separate map app for every city in the world instead of a single worldwide map that allows users to search any city)." Apple's suggested alternative is: "consider submitting a single app and providing the variations using in-app purchase." 4.3(a) carries the key icon, so it also applies to notarization of iOS and iPadOS apps distributed outside the App Store.

The rejection text developers usually receive is: "Guideline 4.3(a) - Design - Spam. We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences." There are three triggers in that sentence (binary, metadata, concept), and any one of them can cause the rejection.

How is 4.3(a) different from 4.3(b) and 4.2.6?

4.3(a) is about duplicates, 4.3(b) is about apps that add nothing new to an already crowded category, and 4.2.6 is about template-built apps submitted by the wrong account. Each one needs a different fix, so check the exact guideline number in your rejection first.

The live text of 4.3(b) also warns that Apple "may remove these apps from the App Store going forward if they are not updated, improved, or do not attract customers", and that low-effort categories such as drinking games and fart apps can lead to removal from the Apple Developer Program if submitted repeatedly. For the other rules Apple revised recently, see our October 2026 App Review Guidelines changes.

Why do template and AI-generated apps get flagged as spam?

Template and AI-generated apps get flagged because many of them share the same starter code, the same screen layouts and similar store copy, which matches all three of the binary, metadata and concept triggers. Owning the code does not exempt an app if the result looks like hundreds of others.

AI app builders often produce the same onboarding, the same tab bar and the same generic feature set ("track habits, get AI insights"), and the generated App Store description often reads the same as well. If you published through a builder, check who appears as the seller. 4.2.6 says template services "should not submit apps on behalf of their clients", so the app should go out under the content owner's developer account. Our Base44 publishing guide and Lovable publishing guide cover what remains your job after export.

What have other developers done to fix a 4.3(a) rejection?

Publicly reported cases show that visual changes alone rarely work. Consolidating duplicate apps and writing a specific reply about what makes the app different work better.

• Merging into an existing app (GitHub). A team shipping a Linphone-based VoIP app reported in linphone-iphone issue #936 that a new icon set and colour scheme did not clear 4.3(a). They concluded the conflict was another Linphone-based app on the same account. They put the changes into that existing app as an update, and it passed "almost straight away".
• Explaining uniqueness (Godot Forum). A game developer on the Godot Forum suspected the shared engine binary was matching other Godot games. Shrinking the build and explaining that it used Godot were both rejected. A reply "listing key areas which I thought made my game enjoyable & unique from other games in the same genre" got it approved.
• Screenshots weren't enough (Apple Developer Forums). In an Apple Developer Forums thread, one developer said an Apple representative pointed to the screenshots, and that "metadata" can mean title, subtitle, keywords or screenshots. Completely new screenshots still got the same rejection, on an update to an app that was 2–3 years old.

The common thread: cosmetic changes (icons, colours, screenshots) failed in all three cases. What worked was removing the duplicate on the account or giving the reviewer concrete, feature-level reasons the app is different.

How do you fix a 4.3(a) rejection step by step?

To fix a 4.3(a) rejection, first find the duplicate, then make real product changes, then reply to App Review with specifics before you resubmit. Resubmitting the same build with a new icon is the most common way to get rejected again.

1. Read the exact guideline number in the App Review section of App Store Connect. If it says 4.2.6 or 4.3(b), follow that row of the table above instead.
2. List every app on your account, live or removed, that shares code, a template, a concept or a design with the rejected one. If you find one, merge them into a single app with in-app variations, or ship the changes as an update to the live app.
3. Search the App Store for your category keywords and note the top results. Write down what your app does that none of them do.
4. Change at least one core flow (data source, main feature, interaction model), not just the theme.
5. Rewrite the name, subtitle, keywords, description and screenshots so they describe your specific features and no generic template copy is left.
6. Reply in App Store Connect using the template below. Apple's App Review page also offers 30-minute Webex appointments if you want to ask a reviewer about the guidelines directly.
7. If you believe the reviewer misunderstood the app, file one App Review Board appeal. Apple asks you to "Submit only one appeal per submission that didn't pass review" and to respond to information requests first.

What should the reply to App Review say?

A good reply names the specific features that make the app different, confirms there are no duplicate apps on your account, and points the reviewer to where each difference can be seen. Keep it short, factual and polite.

Hello App Review,

Thank you for the feedback on Guideline 4.3(a). We have reviewed our account
and confirm [App Name] is our only app in this category. [We removed /
merged "Old App" into this app in version X.Y.]

What [App Name] does that similar apps do not:
1. [Feature] - e.g. syncs with the user's school timetable via [API];
   see Home > Schedule.
2. [Feature] - e.g. offline lesson plans authored by our team, not
   generated or scraped; see Library.
3. [Feature] - e.g. teacher-to-parent messaging; see the demo account.

This version also changes [core flow] and replaces all metadata and
screenshots to reflect these features.

Demo account: [username] / [password]

We are happy to provide more detail or join a call.

Thank you,
[Name]

If a feature sits behind a login, give the reviewer working credentials. Our App Store review demo account guide shows how to set one up.

What should a differentiation checklist cover before resubmitting?

A differentiation checklist should cover your account, your binary, your metadata and your concept, the four places 4.3 looks. Tick every item before you press Submit for Review again.

• Account: no other app, live or removed, shares the same template, concept or design.
• Account: the app is submitted by the content owner's own developer account (4.2.6).
• Binary: template sample screens, demo data and placeholder branding are removed.
• Binary: at least one core feature exists that the top category results lack.
• Metadata: name, subtitle and keywords describe your specific value, not the category in general.
• Metadata: screenshots show your distinguishing features in the first two frames.
• Concept: you can state in one sentence why a user would pick this app over the top five results.
• Review notes: the differences and a demo account are listed, so the reviewer does not have to look for them.

If you've been rejected under 4.3 more than once and aren't sure what to change, our App Store submission service prepares the review and works through rejection feedback with you, for $599 covering both stores (developer account fees are separate).