Guideline4.3

Guideline 4.3 After Using Template or Purchased Source

§ 01What this rejection usually means

If the project began as a template, 4.3 is the expected risk, not a surprise. Changing the display name and primary color does not make a new binary in Apple’s eyes.

§ 02What Apple’s wording tells you

App Review
We noticed your app shares a similar binary, metadata, and/or concept with apps submitted to the App Store.

Assume they have already approved or rejected the same skeleton. Your job is to show what you rewrote, or accept that this skeleton will not pass.

§ 03Common causes

  • CodeCanyon / GitHub / app-builder projects sold to many developers.
  • Only brand, color, and API keys were changed.
  • Default onboarding, tab bar, and IAP screen left intact.
  • Sample assets and class names still in the bundle.

§ 04How to diagnose your case

  1. Diff your tree against the vendor zip. If most files are untouched, a reply will not save this version.
  2. Search the store for the vendor’s own demo app.
  3. Decide whether you can rewrite the shared shell or should stop submitting this skeleton.

§ 05What to inspect in your project

  • Vendor README, license, and default bundle ID still in the repo
  • Unchanged storyboards, SwiftUI templates, and helper names
  • Default icon, launch screen, and onboarding illustrations
  • Shared IAP manager and settings controller

§ 06What not to do

  • Do not submit five brands from the same zip.
  • Do not tell Apple the source is original if it is not.
  • Do not only change the bundle ID.

§ 07How to fix it

  1. Replace navigation, onboarding, and the home information architecture.
  2. Remove unused vendor modules.
  3. Reshoot every store asset from the new UI.
  4. If you cannot rewrite it, do not resubmit.

§ 08How to verify the fix

  • A side-by-side with the vendor demo should not share layout or class names you still ship.
  • Bundle search for the vendor’s product name is empty.

§ 09What evidence to prepare

  • A list of modules you replaced
  • Dates of the rewrite
  • New screenshots so review does not see the demo theme

§ 10Suggested reply to App Review

Resolution Center · Reply
Hello App Review,

We understand 4.3 can trigger on widely distributed starter projects.

This submission is no longer a recolor of a vendor template. We replaced [navigation / onboarding / home / purchase flow], removed unused vendor modules, and rebuilt store metadata from the current UI.

The remaining third-party code is limited to [SDKs], not a white-label app shell.

Thank you.

§ 11Should you appeal?

Do not appeal a barely rebranded template. Appeal only after a substantial rewrite is still matched to the old skeleton.

§ 12Questions people ask next

Is using a template forbidden?
No, but submitting the same app with a new coat of paint is exactly what 4.3 is for. The template is a starting point, not a shippable product.

Related scenarios

Related rejection wording

Related cases