What a Guideline 4.3 rejection actually means
A Guideline 4.3 rejection means App Review decided your submission adds redundancy to the App Store rather than something new. Apple files 4.3 in the Design chapter under the heading Spam, and it holds two clauses cited for two completely different problems. Find out whether you were cited under 4.3(a) or 4.3(b) before changing anything, because the fix for one does nothing for the other.
Read the guideline in Apple's own words rather than someone else's summary. The App Review Guidelines are public and 4.3 takes a minute to read. Most confusion here comes from developers arguing against a version of the rule Apple did not write.
4.3(a): the same app submitted more than once
4.3(a) targets one behaviour: creating multiple Bundle IDs of the same app. Apple's example is a separate map app for every city instead of one worldwide map that lets users search any city. The stated reason is discovery: near-identical apps make it harder for users to find what they want.
If your app has variations for locations, teams, universities or clients, Apple's stated remedy is one app providing those variations inside it, using in-app purchase where the variants are paid. This clause catches developers running a portfolio rather than a product, and it is the easier of the two to fix. It does not care that each build holds different content: different city, same app.
4.3(b): indistinguishable from what is already there
4.3(b) is the clause most people mean when they say they got hit with 4.3. Apple's instruction is not to submit apps indistinguishable from what is already widely available, on the stated grounds that opportunistically creating variants of existing categories or popular apps degrades discovery, reduces app quality, and harms users and developers.
What makes this clause unusually concrete is that Apple names categories. It calls dating, flashlight, sound effects, wallpaper, simple timers and fortune telling well established, and will not accept new submissions in them without a meaningfully different or improved experience. A second list is harsher: drinking games, Kama Sutra, fart and burp apps are called low-quality or low-effort, and repeated submissions of that kind may lead to removal from the Apple Developer Program.
- If your category is on Apple's named list, assume the answer is no and the burden is on you to show the difference.
- Meaningfully different is Apple's phrasing, and the operative word is meaningfully. A new palette, icon and description do not clear it.
- The comparison is against what is widely available, not one specific app. You can be cited under 4.3(b) having copied nobody.
Why template and reskin builds get caught
Reskins fail for a reason easy to miss: the guideline catching them is often not 4.3. Apple's template rule lives in 4.2.6, under Minimum Functionality: apps created from a commercialized template or app generation service will be rejected unless submitted directly by the provider of the app's content. That wording matters. It is not a ban on templates, it is a rule about who submits.
In practice a reskin can attract 4.2.6, 4.3(b) and sometimes 4.1 at once, because these rules overlap without being identical. A reskin of a popular app in a crowded category is all three, and your rejection names whichever the reviewer led with.
Which guideline your rejection is actually about
| Guideline | What it targets | What it is not |
|---|---|---|
| 4.1 Copycats | Copying a specific app, or minor changes to its name or UI | Not about crowded categories generally |
| 4.2 Minimum Functionality | Repackaged websites, or apps without adequate utility | Not about similarity to other apps |
| 4.2.6 Templates | Template services submitting on behalf of clients | Not a ban on using a template yourself |
| 4.3(a) Spam | Multiple Bundle IDs of the same app, such as one per city | Not a judgement about quality |
| 4.3(b) Spam | Being indistinguishable from what is widely available | Not about copying one named competitor |
Why an app can pass once and fail later
- Every submission is reviewed again. Approval of 1.2 is no licence for 1.3, and anything the last reviewer let through is back in scope.
- 4.3(b) is forward-looking. Apple states it may remove apps in established categories that are not updated, improved, or attracting customers.
- The category moves underneath you. An app novel at launch can become indistinguishable without changing a line.
- Your portfolio grows. 4.3(a) risk does not exist at one app. It appears around app three, when the pattern across the account is visible.
- Metadata repositions you. Chasing a high-volume search term in your title and keywords can move you into a saturated category though the binary never changed.
What differentiation looks like to a reviewer
A reviewer spends a short time in your app and judges from what is on screen. Differentiation living in your architecture, roadmap or intentions does not exist here. It has to be legible in the first minute, to someone with no context.
What triggers 4.3 versus what actually resolves it
| What triggers it | What does not fix it | What actually fixes it |
|---|---|---|
| A crowded category with a familiar core | A new theme, icon and colour scheme | A distinct core interaction, or a job the category does not do |
| One app per city, team or client | Renaming bundles or staggering submissions | One app with the variants inside it |
| A generic feature set | A longer list of the same features | Depth in one thing a defined audience needs |
| Content anyone could assemble | More of the same content | Original content the app owns and maintains |
| A listing like every competitor | Better marketing copy | Screenshots showing what only your app does |
| Nothing an existing app cannot do | Arguing your version is better built | A named audience the incumbents do not fit |
The useful question is not whether your app is different. It is whether a stranger could name the difference after a minute of use. If the answer is no, you have a build problem, not a review problem, and no Resolution Center message will fix it.
How to answer a 4.3 rejection in Resolution Center
Resolution Center is a direct conversation with the review team about one submission, and the quality of your reply affects the outcome. Give the reviewer concrete grounds to revise their assessment, rather than saying how the rejection made you feel.
- Name the clause you were cited under and address that one. Answering 4.3(b) when cited under 4.3(a) reads as though you never read it.
- State what your app does that the alternatives do not, in checkable terms. Name the feature, the screen, the audience.
- Point the reviewer at where to look. A feature three taps deep earns nothing if they never reach it.
- Offer a short demo video or demo account when the value is not obvious on a cold launch. This often turns the decision.
- Ask a direct question if the reason is vague. Asking which aspects were considered indistinguishable beats defending the whole app.
- Answer any request for additional information before escalating. Apple's own appeal guidance asks you to do this first.
Appeal or rebuild
Apple's appeal route exists for one situation: you believe your app's concept and functionality were misunderstood, or that you were treated unfairly during review. That is a narrow door, and the right one when the rejection rests on a factual error, such as a reviewer describing a feature you do not have.
Apple asks for specific reasons why you believe the app complies, and for one appeal per submission that did not pass. It publishes no turnaround time for the App Review Board, only that the Board contacts you once its investigation is complete. Do not build a launch date on an assumed window.
Rebuild when the rejection is factually correct and you simply disagree with it. If your app really is a competent version of something that exists, appealing asks a second group to reach the same conclusion. The faster path is finding the narrower audience you can serve better, then building the one feature they cannot get elsewhere.
Short, practical drops on app ideas, validating fast, store listings, and passing app review. No spam, unsubscribe anytime.
Frequently asked questions
How long does a Guideline 4.3 appeal take?
Apple does not publish a turnaround time for the App Review Board. The documented process is that the Board contacts you once its investigation is complete, so the honest answer is that it varies. Apple publishes that on average 90 percent of submissions are reviewed in under 24 hours, but that describes ordinary review, not appeals.
Does a 4.3 rejection put my developer account at risk?
A single rejection targets one submission, not your account. The risk is tied to repetition: 4.3(b) says repeated submissions of low-quality or low-effort apps may lead to removal from the Apple Developer Program, and 4.1(b) says the same about apps impersonating other services. One rejection answered properly is routine.
What is the difference between Guideline 4.1 and Guideline 4.3?
4.1 Copycats is about a specific app you copied, including minor changes to its name or UI passed off as your own. 4.3 Spam is about redundancy rather than theft: multiple Bundle IDs of one app under 4.3(a), or being indistinguishable from what is widely available under 4.3(b). You can be cited under 4.3 having copied nobody.
Can I fix a 4.3 rejection by changing the design and resubmitting?
Rarely, if the change is cosmetic. 4.3(b) asks for a meaningfully different or improved experience, and a new colour scheme, icon and description do not meet it. What changes the outcome is a different core function, distinct content, or a specific audience your app serves in a way the alternatives do not.
I used a template or app builder. Does that mean an automatic rejection?
Not automatically, and the relevant guideline is usually 4.2.6 rather than 4.3. That clause rejects apps created from a commercialized template or app generation service unless they are submitted directly by the provider of the app's content. If you built your own app on a template and own the content, it is not aimed at you. The risk is that template builds often land in a crowded category anyway.
My app was approved before and this update was rejected under 4.3. Why?
Every submission is reviewed again, by someone who did not necessarily approve your last version, so approval does not carry forward. Beyond that, 4.3(b) is forward-looking: Apple states it may remove apps in established categories that are not updated, improved, or attracting customers.
Last reviewed by David on August 20, 2026
