# Guideline 4.3(a) - Design: Spam - Same App Under Multiple Bundle IDs

**Guideline:** 4.3 · **Store:** Apple App Store · **Severity:** high · **Fix difficulty:** hard · **Typical turnaround:** 1-3 days

Canonical URL: https://appstorereject.com/rejections/apple/4/guideline-43a-design-spam-same-app-under-multiple-bundle-ids

## Description

Apple is rejecting your app because they have identified it as substantially similar to another app already on the App Store — either one you've submitted yourself or one from another developer. Guideline 4.3 targets app spam: submitting the same app multiple times under different names, bundle IDs, or developer accounts to game search rankings or saturate a category. This rejection most commonly hits developers who white-label their app for multiple clients (submitting essentially the same binary with different branding), developers who submit regional variants of the same app as separate listings, or developers who create multiple apps with minor feature differences to occupy more search result slots. Apple's automated systems now detect binary similarity, shared code signatures, and matching asset patterns across submissions. Even if you change the app name, icon, and color scheme, if the underlying binary is substantially the same, Apple will flag it. The fastest compliant path is to consolidate your apps into a single listing with in-app configuration (e.g., region selection, brand theming, or account-based customization). If you genuinely have different apps for different audiences, you need to demonstrate clear, substantial differentiation — different features, different content, different user flows — not just different skins.

## Common variations

- App is substantially similar to other apps submitted by you
- Submitting multiple versions of the same app is considered spam
- Apps share the same binary with superficial differences
- White-labeled apps with different branding but identical functionality
- Continued submissions of duplicate apps may result in account removal

## Example rejection email

```
Guideline 4.3 - Design - Spam

We noticed that your app is substantially similar to other apps previously submitted by you or another developer, which is considered a form of spam on the App Store.

Submitting multiple versions of the same app or apps that provide a duplicative experience creates clutter on the App Store and is not in the best interest of users.

Apps that are simply the same app with different branding, or apps that share the same binary with superficial differences, may be removed from the App Store, and continued submissions of this nature may result in the removal of your Apple Developer account.

Next Steps:
Please consolidate your apps into a single app and use in-app configuration to support different brands, regions, or use cases. If you believe your apps are substantially different, reply with a detailed explanation of the unique features, content, and user experience each app provides.
```

## Resolution steps

## Quick Assessment
- **Risk level:** High — this rejection carries account termination warnings
- **Resolution path:** Consolidate into single app OR demonstrate substantial differentiation
- **Typical turnaround:** 1-3 days

## The Fix

### Path A: Consolidate (recommended)
01. **Create a single universal app** — Build one app that supports multiple brands, regions, or configurations through in-app settings.

02. **Implement in-app brand switching** — Let users select their brand/organization during onboarding. Store the configuration and adjust UI theming, content, and backend endpoints accordingly.

03. **Remove duplicate listings** — After your consolidated app is approved, remove the duplicate app listings from App Store Connect.

04. **Redirect existing users** — Use the remaining listings to display an update message directing users to the consolidated app before removing them.

### Path B: Demonstrate differentiation
01. **Document unique features per app** — Create a feature comparison matrix showing what each app does differently. Apple wants to see distinct functionality, not just different content.

02. **Differentiate the user experience** — Different workflows, different interaction models, different navigation structures. Skin-deep changes (colors, logos, copy) don't count.

03. **Target different audiences** — Each app should serve a genuinely different user need. 'Restaurant A' and 'Restaurant B' are the same need; 'Restaurant ordering' and 'Kitchen management' are different needs.

04. **Respond with evidence** — In the Resolution Center, provide detailed screenshots and feature lists for each app showing the substantial differences.

## Prevention
- Default to a single configurable app rather than multiple similar apps
- If you must have separate apps, ensure each has at least 3-5 features the others don't have
- Don't submit more than one app per week with similar functionality
- Use different codebases or substantially different modules for genuinely different products

## Appeal guidance

Appeal only if the apps are genuinely different products with distinct functionality, content, and user bases. Provide a detailed feature comparison matrix showing the differences. If the apps are truly the same app with different branding, do not appeal — consolidate and resubmit.

## Before / after examples

**Before:** Developer has 8 city guide apps (NYC Guide, LA Guide, Chicago Guide, etc.) each with the same binary, UI, and features — just different city data loaded from a config file
**After:** Single 'City Guide' app with city selection on first launch, all cities available in-app with the ability to switch or add favorites, unified notification preferences per city
**Why it works:** Multiple apps with the same binary and different data configurations must be consolidated into a single app with in-app selection.

## Common questions

**Can you appeal a 4.3 rejection?**

Appeal only if the apps are genuinely different products with distinct functionality, content, and user bases. Provide a detailed feature comparison matrix showing the differences. If the apps are truly the same app with different branding, do not appeal — consolidate and resubmit.

**How long does this typically take to fix?**

Typical turnaround is 1-3 days (difficulty: hard). After resubmission, most re-reviews complete within 24-48 hours.

---
*Machine-readable source: https://api.appstorereject.com/api/rejections/detail?slug=guideline-43a-design-spam-same-app-under-multiple-bundle-ids*