Run a free ShipCheck before you resubmit. Paste a public GitHub link or upload a zip, no account needed. ShipCheck reads allowlisted config files and names each issue with the guideline, a short label, how serious it is, and how many places. It can catch other review problems that often show up on the next pass, including in-app account deletion (5.1.1(v)), privacy manifests (5.1.2), In-App Purchase (3.1.1), Sign in with Apple (4.8), and placeholder text or dead links (2.1). A fix is $9, or 3 for $19, paid first. Run a free ShipCheck
Its 4.3 check only looks inside this project: more than one bundle ID that reads as the same app, wording that calls the app a clone, or a saturated category with no distinct experience in the files. It can't compare your app to other App Store listings, score uniqueness against the store, or see the other Bundle IDs on your account. A clean scan isn't a 4.3 clearance.
Guideline 4.3 spam rejection: 4.3(a), 4.3(b), and how to reply
A 4.3 message is frustrating on a first app, because "spam" sounds like Apple thinks you did something shady. Often the reviewer is saying the app looks too close to something already on the store, or too close to another app on your account. You can get through this if you figure out which clause they cited, then combine listings, make a real difference in the product, or explain a difference that's already there.
Read the full message in App Store Connect before you change a line of code. The clause number and the description don't always line up the way you'd expect.
What Apple's rules say
From Apple's App Store Review Guidelines, 4.3 Spam (page marked "Last Updated: October 16, 2026", fetched Nov 18, 2026):
(a) 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). This practice results in unnecessary apps, which makes it hard for users to find the apps they want. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and providing the variations using in-app purchase.
(b) Don't submit apps that are indistinguishable from what's already widely available. Opportunistically creating variants of existing app categories or popular apps degrades App Store discovery, reduces overall app quality, and harms both users and developers. Certain kinds of apps, such as dating, flashlight, sound effects, wallpaper, simple timers, and fortune telling, are well established on the App Store and we will not accept new submissions unless they offer a meaningfully different or improved experience. We may remove these apps from the App Store going forward if they are not updated, improved, or do not attract customers. Other kinds of apps, such as drinking games, Kama Sutra, fart, and burp apps, are mediocre, low-quality, or low-effort and do not add value to the App Store. Repeated submissions of this kind may lead to removal from the Apple Developer Program.
Apple's June 8, 2026 developer news post says 4.3(a) "clarifies the basis for the guideline and adds an example," and 4.3(b) "clarifies the basis for the guideline and adds examples." The quotes above are the current text.
A nearby rule, 4.2.6, covers template and generated apps:
Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content. These services should not submit apps on behalf of their clients and should offer tools that let their clients create customized, innovative apps that provide unique customer experiences.
4.2.6 is a different guideline from 4.3, and a message can cite both. Using an AI coding assistant to write your own app is not, by itself, what 4.2.6 describes.
4.3(a), 4.3(b), and 4.2.6
Start with the letter in front of you.
If it cites 4.3(a): the published text is about multiple Bundle IDs of the same app. List every live, in-review, or removed-from-sale app on the same developer account that shares the same core product: the same gameplay loop, the same content set, or the same utility with only a city, team, or skin change. If you have several of those, Apple's guidance is to ship one app and put the variations inside it, including with in-app purchase.
Some 4.3(a) messages also describe a similar binary, metadata, or concept to other App Store apps, or to other apps you've already submitted, with only minor differences. Answer that description directly. The published 4.3(a) text is the Bundle ID rule; the published 4.3(b) text is the "indistinguishable from what's already widely available" rule. Your reply should address what the reviewer actually wrote.
If it cites 4.3(b), or 4.3 with no letter: this is the uniqueness test. Apple names dating, flashlight, sound effects, wallpaper, simple timers, and fortune telling as categories that are already well established, and says new submissions in those categories need a meaningfully different or improved experience. Other crowded categories can get the same reading even when they aren't on that list. A new wallpaper app, a simple timer, or a thin copy of a popular utility has a high bar.
If it also cites 4.2.6, or talks about a repackaged template: treat that as a separate issue. Show that you submitted the binary, and that the experience is yours: your content, your flows, your features. Changing the name, icon, and colors isn't enough if the app still matches a common template.
If the clause still isn't clear, reply and ask which clause they mean and which apps, if any, they're comparing you to. Don't guess and rebuild the wrong thing.
How to make the app meaningfully different
Apple doesn't publish a checklist for "meaningfully different or improved." The work is in the product, then in how clearly you show that product to the reviewer.
- Write down the core job the app does in one sentence, then how that job differs from a generic app in the same category. If you can't say it without words like "better UI" or "AI-powered," the reviewer probably can't see it either.
- Put that difference on the first screen and in the main flow, not only in the name or the About page. A wallpaper app that only adds a style filter is still a wallpaper app. One with a unique creation flow, original content you own, or a job other than "browse and set a wallpaper" has a clearer case.
- Remove leftover template chrome: placeholder onboarding, sample data, and stock feature sets you don't use. If you used an app generation service, rebuild the flows around your content rather than shipping the default screens with a new coat of paint.
- Update the name, subtitle, description, and screenshots so they show the same difference. Reviewers see the listing and the binary together.
- If 4.3(a) applies because you filed city, team, or client-specific binaries, plan a single app and move those variations into in-app selection or in-app purchase.
Don't invent features in the reply that the build doesn't have. The reviewer will open the app.
Resubmit or appeal
Apple's After You Submit notes say:
If your app has been rejected and you have questions or would like to provide additional information, please use App Store Connect to communicate directly with the App Review team.
If you disagree with the outcome of your review, please submit an appeal.
Apple's appeal help page and App Review page add the process: reply in App Store Connect first, then appeal if that isn't enough. An appeal is appropriate when you believe the app already follows the guidelines, or you were treated unfairly. Cite the specific guideline and explain point by point how the app meets it. Submit only 1 appeal per submission, and address every cited guideline in that appeal. Don't appeal if you've already fixed the issues and resubmitted, and don't use an appeal for a status update or an expedited review. If you're appealing, don't resubmit at the same time. Apple's review status page says resubmitting starts a new review and the appeal will be closed.
A practical split:
- Resubmit a new build when you can change the app so it meets the published text: you've combined duplicate Bundle IDs, or you've actually made the experience different.
- Reply first, then appeal if needed, when you believe the current app already has a meaningful difference, or that 4.3(a) doesn't apply because this is your only binary of this product. Say so with specifics, then use the appeal form if the reply isn't enough.
Apple also says, in After You Submit:
if your app is repeatedly rejected for the same guideline violation or you've attempted to manipulate the review process, review of your app will take longer to complete.
Resubmitting the same binary, or opening a new developer account to get another try, works against you. The guidelines introduction warns that trying to trick the review process, or copying another developer's work, can get apps removed and an account expelled from the Apple Developer Program.
What to write in App Store Connect
People still call this the Resolution Center. In current App Store Connect, you do it in the App Review section. Apple's reply help page lists the steps:
- In Apps, select the app.
- At the top of the page, click the link that indicates there are unresolved issues.
- In the In Progress section, click Resolve next to the submission.
- Click Reply to App Review, write the reply, attach files if you need to, and click Reply.
Apple's contact help page says to be specific about the feature, guideline, or step you need clarified, and to add information that helps App Review understand the app's concept if you think it was misunderstood. Don't use this reply field to file an appeal or request an expedited review. Those have their own forms.
Keep the reply short and concrete. Two templates you can adapt:
If you combined listings or changed the product (and you're sending a new build):
Thanks for the review. Build 8 is a single app for all cities, instead of one Bundle ID per city. City-specific content is now chosen inside the app. The home screen opens on the personalized plan for the user's city, which is the part of the product that isn't a generic city guide. Screenshots and the description were updated to show that flow.
If you believe the current app already meets 4.3(b) (reply first, same build):
Thanks for the review. This is our only app on this account, and we didn't submit variants under other Bundle IDs. The app's core job is [one sentence]. That differs from a typical [category] app because [specific flow or content the reviewer can tap], which appears on first launch and on these screens: [names]. We'd be grateful if you could take another look, or tell us which apps you're comparing us to.
(Those are templates. Use your real build number, the actual difference, and the screens a reviewer can open. Don't claim a difference the build doesn't show.)
You can attach screenshots or a short screen recording that starts on the unique flow. If you need more back and forth after they reply, Apple's contact help page says you can request a call, include your time zone, and that calls are typically completed within 3 to 5 business days. Apple's App Review page also offers a 30-minute video appointment to talk through the guidelines.
What about Google Play?
Google Play has its own policies for spam and repetitive content, which are separate from Apple's 4.3. This guide covers App Review only. If Play rejected a similar listing, read the policy named in your Play Console message and reply there.
When ShipCheck helps vs when it doesn't
ShipCheck's 4.3 check only looks inside this project. It flags more than one bundle ID that reads as the same app, wording that calls the app a clone, or a saturated category with no distinct experience in the files. It can't compare your app to other App Store listings, score uniqueness against the store, or see the other Bundle IDs on your account.
It can still help before you resubmit, because a 4.3 resubmission gets a full review of the new build. Its other checks look at project files for problems like missing in-app account deletion (5.1.1(v)), a missing privacy manifest (5.1.2), a Stripe payment sheet with no In-App Purchase library (3.1.1), a missing Sign in with Apple option (4.8), and placeholder text or sample links (2.1). See the guidelines we check.
It can't see your App Store Connect answers, your other apps, or your screenshots.
FAQ
The message says 4.3(a), but this is my only app. What should I do? Reply with that fact, describe the specific difference in the build, and ask which apps, if any, they're comparing you to. If you believe the app already follows the published text and a reply isn't enough, follow Apple's appeal steps above.
Is a wallpaper, timer, or flashlight app automatically rejected? Apple's 4.3(b) text says those categories are well established, and that Apple will not accept new submissions unless they offer a meaningfully different or improved experience. The difference has to be in the experience, not only in the branding.
I built the app with an AI coding tool. Is that 4.2.6? 4.2.6 is about apps created from a commercialized template or app generation service, and about those services submitting apps on behalf of clients. An AI coding assistant isn't automatically that. If the rejection also cites a repackaged template, show how the content, flows, and features are yours.
Should I appeal and resubmit at the same time? No. Apple's review status page says resubmitting starts a new review and closes the appeal. Pick one path.
Will sending the same build again get a different reviewer? Apple doesn't publish that. After You Submit says repeated rejections for the same guideline violation make review take longer. Change the product, or make a specific case that the current product already complies.
Do I need a new build? Yes, if you're changing the app or combining listings. A metadata-only clarification, or an appeal of a decision you disagree with, is a reply (and maybe an appeal), not a new binary.
Related guides
- Guideline 2.1 Information Needed: how to answer App Review and get back in review
- Guideline 2.1 Information Needed: Apple wants a screen recording
- App stuck in Waiting for Review
- Guidelines we check
Ready to resubmit? Run a free ShipCheck first. Paste a public GitHub link or upload a zip, no account needed. It names each issue with the guideline, a short label, how serious it is, and how many places. A fix is $9, or 3 for $19, paid first. Run a free ShipCheck
That 4.3 check still can't see the rest of the App Store, and a clean scan isn't a spam clearance.
