Rejection guides / Guideline 4.3: Spam
Guideline 4.3 - Design - Spam: what it means and how to fix it
4.3 is about duplicates and look-alikes, not bugs. Apple is saying your app isn't different enough, either from your own apps or from what's already on the App Store.
"Don't submit apps that are indistinguishable from what's already widely available."App Review Guideline 4.3(b), Apple
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
4.3(a) and 4.3(b) are different problems
4.3(a) is about duplicates. The guideline asks you not to create multiple Bundle IDs of the same app, and gives the example of a separate map app for every city instead of one app that covers them all. In practice the rejection message often says your app "shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers". That's common with template, white-label and reskinned apps, because the same code ships under many names.
4.3(b) is about saturated categories. Apple names dating, flashlight, sound effects, wallpaper, simple timers and fortune telling as well established, and says it won't accept new ones unless they offer a meaningfully different or improved experience.
Likely causes
- The app was built from a template or white-label codebase that other developers also ship.
- You or a client submitted several versions of one app, for example per city, venue, brand or language.
- The app sits in a category Apple names in 4.3(b) and looks like the many apps already there.
- The binary or listing is close to an app you previously had rejected or removed.
What usually gets it through
- If you ship several near-identical apps, combine them into one app. Apple's own suggestion is a single app with the variations offered in-app.
- If it's built on a template, make the difference real: features, content or experience the template apps don't have. Cosmetic changes such as colours, icons and names rarely clear 4.3.
- Reply to App Review explaining specifically what is unique and who it's for. Point to features they can see in the build.
- If you're an agency shipping the same codebase for many clients, ask whether those clients can publish under one app or under their own developer accounts with genuinely distinct apps.
Appealing to the App Review Board is possible, but a 4.3 appeal works best when the app really is different and the first reviewer missed it.
Common questions
- My app isn't copied from anyone. Why did I get 4.3(a)?
- 4.3(a) rejections often come from shared code. If your app uses a template or white-label base, other apps on the store may share much of the same binary, even if you wrote the idea yourself.
- Will changing the name and icon fix a 4.3 rejection?
- Rarely. Apple compares the binary, metadata and concept, so the changes need to be in what the app does.
- Can repeated 4.3 rejections affect my account?
- Apple's guideline says repeated submissions of low-effort apps in the categories it lists under 4.3(b) may lead to removal from the Apple Developer Program.
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
Related guides
- App Review Board: How to appeal a rejection
- Guideline 4.2: Minimum Functionality
- Guideline 2.1: Information Needed
Apple decides every review. These guides explain what the guidelines say and what usually helps. They can't promise an approval.
Sources: App Review Guidelines (Apple)