Guideline 4.2.6 rejection: Template or app generation service apps
What it means, why it happens, and how developers get through it.
Subject line you may see: Guideline 4.2.6 - Design - Minimum Functionality
What Apple's guideline says
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.
From App Review Guidelines, 4.2.6, as revised October 16, 2026.
Common causes
- An agency or app builder submitting client apps from its own developer account
- Many apps from the same template with only the content changed
- A template app with little custom functionality
How to fix it
- Have the business that provides the content submit the app from its own developer account
- Or combine clients into one app that lets users pick their content (Apple calls this an aggregated or picker model)
- Add features made for this customer, not only new content
- Reply explaining who owns the content and who submitted the app
What to put in your reply
A sample reply note. Replace the brackets with your facts and remove anything that does not apply.
Hello, Thank you for the review. Regarding Guideline 4.2.6, the app is now submitted by [business], the provider of its content, from its own developer account. [Or: we combined client apps into one app with a picker.] Thank you.
Real cases: others who got 4.2.6
No public cases logged yet.
Questions developers ask about 4.2.6
What does a Guideline 4.2.6 rejection mean?
Your app was built with a commercial template or app builder and was not submitted by the business whose content it carries, or it is one of many near-identical client apps.
Why do apps get rejected under Guideline 4.2.6?
Common causes, based on Apple's guideline text: an agency or app builder submitting client apps from its own developer account; many apps from the same template with only the content changed; A template app with little custom functionality.
How do I fix a Guideline 4.2.6 rejection?
1. Have the business that provides the content submit the app from its own developer account. 2. Or combine clients into one app that lets users pick their content (Apple calls this an aggregated or picker model). 3. Add features made for this customer, not only new content. 4. Reply explaining who owns the content and who submitted the app.
Do I need a new build for Guideline 4.2.6?
Change the product, not the wording. Appeals rarely move this one. Make visible differences, then resubmit with a short reply and a review path. This is how the guideline is usually resolved, not a prediction for your app.
How should I reply to App Review about Guideline 4.2.6?
Reply in App Store Connect. Thank the reviewer and name Guideline 4.2.6, say exactly what changed and in which version and build, give a numbered path the reviewer can follow, and attach proof such as screenshots or a screen recording.
Stuck on 4.2.6?
Do it yourself, faster
App Store Rejection Rescue Kit: the full decoder, 12 reply templates, Notes for Review templates, and a 60-point preflight checklist.
Get the kit, $12Have it written for you
Send your rejection, get a reply drafted for your exact case. Kit buyers get $10 off.
AI-assisted, built on Apple's App Review Guidelines. Not a guarantee of approval. If we do not deliver within 24 hours, you get a full refund.
Reply service, $29Related rejections
See also: 4.3(a) spam · 4.2 minimum functionality
Source: Apple's App Review Guidelines, section 4.2.6, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.