· 13 min read · Nadeera Silva
Guideline 4.3 Design Spam: Fix White-Label App Rejections
What Apple's Guideline 4.3(a) and 4.3(b) spam rejections mean, and how to fix them by merging white-label apps, using 4.2.6, or replying and appealing.

Your app comes back from review with "Guideline 4.3(a) - Design - Spam" or "Guideline 4.3(b) - Design - Spam". For agencies and white-label Flutter projects, it usually happens the day the second or third client build is submitted: same code, new name, new colours, new Bundle ID. This post explains what a guideline 4.3 design spam rejection means, the causes Apple and developers report, and the fix: one app with an in-app brand picker, the 4.2.6 route for template apps, or a reply and appeal when the app really is distinct.
Quick answer
Guideline 4.3 design spam means App Review thinks your app is a duplicate: either one of several apps that are really the same app under different Bundle IDs (4.3(a)), or a new entry in a category that already has plenty of near-identical apps (4.3(b)). If you ship one codebase as several branded apps, merge them into a single app where users pick their brand, location or team inside the app, then reply to App Review saying so. If the app is genuinely your own and distinct, reply with specific differences, and appeal to the App Review Board only if that reply fails.
What this means for your app or business
A 4.3 rejection is not about a bug. Apple is saying the store does not need another copy, so resubmitting the same build with a new icon rarely changes the answer.
- Cost: merging several white-label apps into one is, in my estimate, a few days to two weeks of work, depending on how much the brands differ. A reply for a distinct app takes a few hours.
- Risk: Apple's guideline says repeated submissions of low-value apps in crowded categories "may lead to removal from the Apple Developer Program". Developers have also posted 4.3 rejection messages that add an "Extended Review" warning for repeat submissions.
- Timeline: replies and appeals can take days to weeks. One team on the Apple Developer Forums reported no answer 10 days after a 4.3 reply in 2026.
- When to get help: you have two or more apps from one codebase, you bought a template, or you have already been rejected twice with the same message.
What does Guideline 4.3 Design Spam say?
Section 4.3 of the App Review Guidelines has two parts.
4.3(a) starts: "Don't create multiple Bundle IDs of the same app". Apple's example is a separate map app for every city instead of one worldwide map, and it suggests that apps with versions "for specific locations, sports teams, universities, etc." should consider "submitting a single app and providing the variations using in-app purchase."
4.3(b) starts: "Don't submit apps that are indistinguishable from what's already widely available." It names dating, flashlight, sound effects, wallpaper, simple timers and fortune telling as well established categories where Apple will not accept new apps "unless they offer a meaningfully different or improved experience."
In messages developers have posted publicly in 2026, the 4.3(a) rejection reads: "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." Variants say "by you or other developers" or "by a terminated Apple Developer Program account". That phrase tells you whose apps yours was compared with.
How do 4.3(a), 4.3(b) and the related guidelines compare?
| Guideline | What Apple objects to | Typical trigger | Main fix |
|---|---|---|---|
| 4.3(a) Spam | Several Bundle IDs of the same app, or a binary, metadata or concept similar to other apps | One Flutter project shipped as an app per client, city or team | One app with variations chosen inside it |
| 4.3(b) Spam | An app indistinguishable from what is already widely available | A plain dating, wallpaper, timer or fortune telling app | A meaningfully different experience, shown early |
| 4.2.6 Template apps | Apps from a commercial template or app generator not submitted by the content owner | An agency submitting client apps from its own account | Client submits under its own account, or one "picker" app |
| 4.1 Copycats | Copying another app's name, UI or brand | Minor changes to a popular app | Your own concept, name and assets |
Why does App Review flag an app as spam?
Apple's App Review page lists "Repeated submission of similar apps" as a common issue, says it "ties up the App Review process", and asks developers to combine such apps into one.
The rejection message adds a list. In the full 4.3(a) text Josh Dance published for an update to his 2018 app, Apple says factors "may include":
- Submitting an app with the same source code or assets as other apps already submitted
- Creating and submitting multiple similar apps using a repackaged app template
- Purchasing an app template with problematic code from a third party
- Submitting several similar apps across multiple accounts
Developer reports on the Apple Developer Forums (individual accounts, not Apple policy):
- White-label builds. A 2019 thread asked about shipping rebranded copies with different Bundle IDs from one account. A reply pointed out that 4.3 names this exact case.
- Shared engine or SDK code. A game developer reported that on a call, App Review said its system had found a "binary match" with another developer's game, which could come from code, assets, shared engine code, ad SDKs or third-party libraries.
- A Flutter app with no template. The developer of a passport photo app reported a 4.3(a) rejection although their own audit found only standard Flutter generated files in common with their other apps.
- Several apps at once. A solo developer reported five unrelated apps rejected in the same minute under 4.3 and 4.2.6, each with the same questions about audience, shared code and templates.
The most common white-label shape is simpler: one Flutter project, several flavors, one Apple account. That is the textbook 4.3(a) case, and it is fixable.

How do I fix a white-label Flutter app rejected under 4.3(a)?
1. Count the apps your repo really ships
Run this from the project root. If you see more than one iOS Bundle ID (ignoring tests), you have the 4.3(a) shape.
#!/usr/bin/env bash
# list-app-ids.sh: how many separate store apps does this one Flutter repo ship?
# Run from the project root. More than one line per platform is a 4.3(a) warning sign.
echo "iOS bundle IDs:"
grep -rhoE 'PRODUCT_BUNDLE_IDENTIFIER *= *[^;]+' \
ios/Runner.xcodeproj/project.pbxproj ios/Flutter/*.xcconfig 2>/dev/null \
| sed -E 's/.*= *//; s/"//g' | grep -v 'RunnerTests' | sort -u
echo "Android application IDs and suffixes:"
grep -rhoE 'applicationId(Suffix)? *=? *"[^"]+"' android/app/build.gradle* 2>/dev/null | sort -u2. Turn flavors into data
Pick one Bundle ID and one store name that describes the product, not a single client ("Clinic Finder", not "Kandy Smile Clinic"). Each brand becomes a record: name, colour, logo URL, API tenant. The user picks it on first launch, and the app remembers the choice.
A complete lib/main.dart for this pattern. I ran flutter analyze and two widget tests on it (picker, saved choice, switching).
// One App Store app for every client brand (Guideline 4.3(a) / 4.2.6 "picker" model).
// The brand is data chosen inside the app, not a separate flavor and Bundle ID.
import 'package:flutter/material.dart';
import 'package:shared_preferences/shared_preferences.dart';
class Brand {
const Brand({
required this.id,
required this.name,
required this.city,
required this.color,
required this.apiBase,
});
final String id;
final String name;
final String city;
final Color color;
final String apiBase;
}
// In production, load this list from your API so a new client needs no new build.
const brands = <Brand>[
Brand(
id: 'colombo-dental',
name: 'Colombo Dental',
city: 'Colombo',
color: Color(0xFF0F766E),
apiBase: 'https://api.example.com/t/colombo-dental',
),
Brand(
id: 'kandy-smile',
name: 'Kandy Smile Clinic',
city: 'Kandy',
color: Color(0xFFB45309),
apiBase: 'https://api.example.com/t/kandy-smile',
),
Brand(
id: 'galle-care',
name: 'Galle Family Care',
city: 'Galle',
color: Color(0xFF1D4ED8),
apiBase: 'https://api.example.com/t/galle-care',
),
];
class BrandStore {
static const _key = 'selected_brand_id';
Future<Brand?> load() async {
final prefs = await SharedPreferences.getInstance();
final id = prefs.getString(_key);
for (final b in brands) {
if (b.id == id) return b;
}
return null;
}
Future<void> save(Brand? brand) async {
final prefs = await SharedPreferences.getInstance();
if (brand == null) {
await prefs.remove(_key);
} else {
await prefs.setString(_key, brand.id);
}
}
}
void main() {
WidgetsFlutterBinding.ensureInitialized();
runApp(OneApp(store: BrandStore()));
}
class OneApp extends StatefulWidget {
const OneApp({super.key, required this.store});
final BrandStore store;
@override
State<OneApp> createState() => _OneAppState();
}
class _OneAppState extends State<OneApp> {
Brand? _brand;
bool _loading = true;
@override
void initState() {
super.initState();
widget.store.load().then(
(b) => setState(() {
_brand = b;
_loading = false;
}),
);
}
Future<void> _select(Brand? b) async {
await widget.store.save(b);
setState(() => _brand = b);
}
@override
Widget build(BuildContext context) {
final seed = _brand?.color ?? const Color(0xFF0F766E);
return MaterialApp(
title: 'Clinic Finder', // one store name for the whole product
theme: ThemeData(colorSchemeSeed: seed),
home: _loading
? const Scaffold(body: Center(child: CircularProgressIndicator()))
: _brand == null
? BrandPicker(onSelected: _select)
: BrandHome(brand: _brand!, onSwitch: () => _select(null)),
);
}
}
class BrandPicker extends StatelessWidget {
const BrandPicker({super.key, required this.onSelected});
final ValueChanged<Brand> onSelected;
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(title: const Text('Choose your clinic')),
body: ListView(
children: [
for (final b in brands)
ListTile(
leading: CircleAvatar(backgroundColor: b.color),
title: Text(b.name),
subtitle: Text(b.city),
onTap: () => onSelected(b),
),
],
),
);
}
}
class BrandHome extends StatelessWidget {
const BrandHome({super.key, required this.brand, required this.onSwitch});
final Brand brand;
final VoidCallback onSwitch;
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: Text(brand.name),
actions: [
IconButton(
tooltip: 'Switch clinic',
icon: const Icon(Icons.swap_horiz),
onPressed: onSwitch,
),
],
),
body: Center(child: Text('Bookings for ${brand.name}, ${brand.city}')),
);
}
}In production, load the brands list from your API so adding a client is a database change, not a new build. A universal link such as https://yourdomain.com/c/kandy-smile can open the app with a brand preselected.
3. Handle paid variants inside the app
Apple's own suggestion in 4.3(a) is in-app purchase for variations. If some brands or locations are premium, sell them as in-app products in the one app (see my guide on fixing in-app purchase product not found in Flutter before you test). If brands are separate businesses whose users log in, an account that maps to a tenant works too.
4. Retire the extra listings
Ship the combined app first, move users across with an in-app notice in the old apps, then in App Store Connect open each old app, go to Pricing and Availability and click Remove App From Sale. Apple says this takes effect in all regions within 24 hours, and existing users keep receiving updates and can redownload from their purchase history (Apple help).
5. Clean up signing and CI
One Bundle ID means one App ID, one set of profiles and one pipeline. If your CI still loops over flavors, simplify it. My post on Codemagic "No matching profiles found" covers the Bundle ID to profile mapping.
What if each client needs its own App Store listing?
That is guideline 4.2.6. 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." That usually means the client enrolls in the Apple Developer Program and publishes a customized app under its own account. The other option Apple names is "a single binary to host all client content in an aggregated or 'picker' model", which is exactly the code above.
How do I reply to App Review or appeal?
Reply first. Apple's contact page says to use Reply to App Review in App Store Connect (older guides call this the Resolution Center), be specific, and add information if you believe the app was misunderstood. You can also request a call there. Apple says calls are typically completed within three to five business days.
If you consolidated, say so. If the app is distinct, list what only it does and where to see it. A template to adapt:
Hello App Review team,
Thank you for the review under Guideline 4.3(a).
What changed: we merged our three clinic apps into this single app. Users choose
their clinic on the first screen (Choose your clinic), and can switch later with the
Switch clinic button. The other apps (<names>) will be removed from sale once
users have moved across.
What is specific to this app: <one or two features that are verifiable in the app>.
Where to see it: <screen and tap path>. Demo account: in App Review Information.
Shared code: the app uses Flutter and standard packages (<list>). It is not built
from a purchased template, and we publish no other app with this concept.
If any specific part still looks similar to another app, please tell us which one
so we can change it.
Kind regards,
<name>, <role>Appeal only when you believe the app follows the guidelines and the reply did not resolve it. The App Review Board page asks you to reply to the rejection first, cite the guideline and explain point by point how the app meets it, submit only one appeal per rejected app, and not appeal if you have already fixed the issue and resubmitted.
How do I verify the fix before resubmitting?
list-app-ids.shprints one iOS Bundle ID and one Android application ID.- A fresh install opens on the picker, and every brand loads its own data.
- The App Store name, subtitle, description and screenshots describe the product, not one client.
- No demo screens or sample assets from a template are reachable.
- Review notes explain the picker and give a demo account (my Guideline 2.1 Information Needed guide shows what reviewers expect).
- The old listings are scheduled for removal, and nothing else from the same codebase is waiting for review.
How do I prevent a 4.3 rejection?
- Decide on one app versus client accounts before you sell a white-label deal, and put it in the contract.
- Keep client differences in data and remote config, not in separate targets.
- For crowded categories, put the feature that is different on the first screen and in the first screenshot, because 4.3(b) asks for "a meaningfully different or improved experience".
Frequently asked questions
What is Guideline 4.3 Design Spam?
It is the App Review guideline against duplicate apps. Part (a) covers several Bundle IDs of the same app and apps that share a similar binary, metadata or concept with others, and part (b) covers apps indistinguishable from what is already widely available.
What is the difference between Guideline 4.3(a) and 4.3(b)?
4.3(a) is about duplicates of the same app, such as one app per city, client or team under separate Bundle IDs. 4.3(b) is about crowded categories, where Apple wants a meaningfully different or improved experience before it accepts another app.
Can I publish white-label apps for several clients from one Apple account?
Apple's guidelines point the other way. 4.3(a) asks for a single app with the variations inside it, and 4.2.6 says template-based apps should be submitted by the content owner or hosted in one aggregated picker app.
Will changing the app icon, name and colours fix a 4.3 rejection?
Usually not. Apple's message says the app is similar with only minor differences, and branding changes are exactly that. Change the distribution, such as one app with an in-app picker, or the product itself.
Should I appeal a Guideline 4.3 rejection?
Reply to App Review first with specific differences. Apple says to appeal to the App Review Board only if you believe the app follows the guidelines after that reply, to file one appeal per app, and not to appeal after resubmitting a fixed build.
Can a Flutter app get a 4.3(a) rejection even if I wrote it myself?
Developers have reported it on the Apple Developer Forums, including a Flutter app whose only shared files were standard generated ones. In that case, reply with what is unique and where to find it, explain what code is shared, and appeal if needed.
What happens to users of the old apps after I merge them?
If you remove an app from sale in App Store Connect, Apple says existing users keep receiving updates and can redownload it from their purchase history. Use an in-app notice in the old apps to move users to the combined app first.
Sources
- App Review Guidelines (4.1, 4.2.6, 4.3 Spam) (Apple Developer, 2026-10-16)
- App Review (Avoiding common issues: repeated submission of similar apps) (Apple Developer)
- Contact App Review for help with a submission (Apple Developer)
- Appeal to the App Review Board (Apple Developer)
- Reply to App Review messages (Apple Developer)
- Manage availability for your app on the App Store (Apple Developer)
- What to do if your app gets rejected for Guidelines 4.3(a) aka 'spam' (Josh Dance)
- White Label apps / Apple 4.3 spam design (Apple Developer Forums)
- Guideline 4.3(a): 5 rejections despite major code and content changes (Apple Developer Forums)
- Guideline 4.3(a) Design Spam rejection: no actionable clarification (Flutter app) (Apple Developer Forums)
- Account flagged under 4.3: five unrelated apps rejected the same minute (Apple Developer Forums)
- No response from App Review for 10+ days after Resolution Center reply (Guideline 4.3) (Apple Developer Forums)
- shared_preferences (pub.dev, 2026-10-05)
Keep reading
- Guideline 2.1 Information Needed: How to Get ApprovedWhat App Store Guideline 2.1 Information Needed asks for on a new app, how to reply without a new build, and how it differs from App Completeness.
- Codemagic iOS Code Signing: No Matching Profiles Found FixWhy Codemagic says no matching profiles were found for your bundle identifier, and how to set up iOS code signing for a Flutter app that ships to TestFlight.
- Flutter In-App Purchase Product Not Found: Fix ChecklistFlutter in_app_purchase returning notFoundIDs or an empty paywall? Work through the App Store and Google Play setup checks in the right order.
Comments
Share a question or note about this article.
Loading comments…