Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Apple rejected the app under Guideline 4.3, Design: Spam

ErrorGuideline 4.3(a) - Design - Spam

Short answer

Guideline 4.3 is Apple's duplicate rule. Part (a) covers one app published under several bundle IDs; part (b) covers apps that are hard to tell apart from what is already widely available, especially in crowded categories. Merge variants into one app, publish client apps from the client's own account, change features rather than colours, then reply in App Store Connect with specific differences.

  • Applies to App Store Connect, App Review Guidelines as updated 16 October 2026, Xcode 26, Flutter 3.50 stable
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Note which part the message cites, (a) or (b), then list every bundle ID your codebase can build. Several IDs from one Flutter project usually means (a); a single ID with a (b) rejection means the idea itself looks like what is already on the store.

    xcodebuild -list -project ios/Runner.xcodeproj
    grep -h "PRODUCT_BUNDLE_IDENTIFIER" ios/Runner.xcodeproj/project.pbxproj | sort -u
  2. 2Match what you see, then jump to its fix

    1. 14.3(a), and your account has the same app per city, branch, team, school or language under different namesOne codebase is published as several appsFix
    2. 24.3(a) on an agency or vendor account that publishes branded versions of the same product for different businessesA white-label app is submitted for each client from one developer accountFix
    3. 3A 4.3 rejection (sometimes with 4.2.6) on an account that has only this one appThe app is built on a purchased template that others also shippedFix
    4. 44.3(b): a flashlight, wallpaper, sound-effect, dating, fortune-telling or simple timer app, or a close copy of a popular titleThe category is saturated and the app adds nothing newFix
    5. 5The same 4.3 rejection comes back after a resubmission, or a reply was ignoredThe reply or resubmission did not show what changedFix

What does the error look like?

  • Guideline 4.3(a) - Design - Spam
  • Guideline 4.3(b) - Design - Spam
  • A second rejection with the same 4.3 text after you resubmitted with new screenshots

Cause 1 of 5

One codebase is published as several apps

1Check

Apple's guideline asks for one app with variations inside it, and names the per-location copy as the example to avoid. Flutter flavors make this easy to do by accident: each flavor gets its own bundle ID, icon and store listing, but the binaries are nearly identical. Compare the schemes and bundle IDs above with the apps listed in App Store Connect.

ls ios/Flutter/*.xcconfig
grep -rn "flavor" lib/main*.dart | head -n 20

2Fix

Ship one app and let the user choose the location, team or brand inside it, loaded from your backend. Apple suggests in-app purchase where the variants are paid content. Remove the extra listings from sale once the combined app is live, so the account no longer holds near-copies.

// one app, variant picked at runtime instead of per-flavor builds
final region = await RegionStore.load() ?? await showRegionPicker(context);
final config = await api.fetchConfig(region: region.id);

3Verify

Only one bundle ID remains in the Release configuration, and the variant switch works without reinstalling.

grep -h "PRODUCT_BUNDLE_IDENTIFIER" ios/Runner.xcodeproj/project.pbxproj | sort -u
Did this fix it?

Cause 2 of 5

A white-label app is submitted for each client from one developer account

1Check

Guideline 4.2.6 says apps made from a commercial template or app generator are rejected unless the provider of the app's content submits them. One account shipping many rebranded binaries reads to App Review as spam even when each client is real. Check which team signs and submits each build.

grep -h "DEVELOPMENT_TEAM" ios/Runner.xcodeproj/project.pbxproj | sort -u

2Fix

Either each client enrols in the Apple Developer Program and the app ships from their account, with you working as a team member, or you publish one 'picker' app that holds every client as an entry inside it, which 4.2.6 lists as acceptable. In both cases, give each client real customisation beyond logo and colours.

# per client: sign with the client's own Team ID
# Xcode > Runner target > Signing & Capabilities > Team

3Verify

The app record sits in the client's App Store Connect account, and the build is signed with their team.

xcodebuild -showBuildSettings -workspace ios/Runner.xcworkspace -scheme Runner | grep DEVELOPMENT_TEAM
Did this fix it?

Cause 3 of 5

The app is built on a purchased template that others also shipped

1Check

Templates sold on marketplaces are bought by many developers, so other copies with the same screens, sample content and icons may already be on the store, and 4.2.6 rejects template-generated apps not submitted by the content owner. A renamed template is hard for a reviewer to tell apart from those copies. Search the store for the template's demo name and screenshots, and scan your project for leftovers.

grep -rniI "lorem ipsum\|demo\|template\|sample" lib/ assets/ ios/Runner/Info.plist | head -n 40

2Fix

Treat the template as a starting point only: replace all bundled art, sample data and copy, rebuild the main flows around your own feature, and drop modules you do not need. Change the store name, description and screenshots so they describe what your app does differently.

# list unused or template-only assets before deleting them
find assets -type f | sort > /tmp/assets.txt
grep -rhoE "assets/[A-Za-z0-9_./-]+" lib/ | sort -u > /tmp/used.txt
comm -23 /tmp/assets.txt /tmp/used.txt

3Verify

No sample content remains, and a side-by-side of your screenshots with the template's demo shows different screens, not recoloured ones.

grep -rniI "lorem ipsum" lib/ assets/ | wc -l
Did this fix it?

Cause 4 of 5

The category is saturated and the app adds nothing new

1Check

Apple's guideline names these categories as already well served and says new entries need a meaningfully different or better experience. Write down in one sentence what your app does that the top results for your keywords do not. If you cannot, App Review cannot either.

curl -s 'https://itunes.apple.com/search?term=white+noise&entity=software&limit=15' | python3 -m json.tool | grep '"trackName"'

2Fix

Build the difference before you resubmit: a feature, workflow or content set that the established apps lack. Then say it plainly in the App Review notes and in the first screenshot, rather than leaving the reviewer to find it.

# App Store Connect > your app > version > App Review Information > Notes
# One paragraph: what is new, where to find it, demo account if needed.

3Verify

The difference is visible in the first minute of use, with no account set-up needed to reach it, and the review notes point straight to it.

Did this fix it?

Cause 5 of 5

The reply or resubmission did not show what changed

1Check

Resubmitting an unchanged build, or changing only icons and screenshots, gets the same answer. Apple says apps rejected again and again for the same guideline take longer to review, and 4.3(b) warns that repeated low-effort submissions can cost the developer account. List what actually changed since the rejected build.

git diff --stat v1.0.0-rejected..HEAD -- lib/ assets/ ios/

2Fix

Reply with 'Reply to App Review' in App Store Connect: name the guideline, explain point by point how the app differs or why the variants were merged, and ask a specific question if the reason is unclear. That field is not for appeals. If you are sure App Review misread the app, file one appeal per app through the App Review Board form after replying, covering every guideline the rejection cites.

Guideline 4.3(a): since build 14 we merged the six city apps into this
single app (cities are chosen on first launch) and removed the others
from sale. New in this build: offline route planning, see Settings > Maps.

3Verify

The submission status in App Store Connect moves back to In Review, and the reply arrives in the same message thread.

Did this fix it?

How do I stop it coming back?

  • Decide before building whether variants belong in one app; changing it after launch costs reviews and ratings.
  • For client work, agree up front that each client owns their developer account and app record.
  • Keep App Review notes current with each submission: what is new, how to reach it, and test credentials.
  • Do not resubmit after a 4.3 rejection until something in the binary has changed.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

Xcode cannot find GoogleService-Info.plist for the Runner target

error: Build input file cannot be found: '/Users/GoogleService-Info.plist' (in target 'Runner' from project 'Runner')

Xcode's project file lists GoogleService-Info.plist as an input, but nothing exists at the path it records.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.