On 16 October 2026 Apple updated the App Review Guidelines. The changes do not look loud: one new rule about creative assets, a separate number for the rule on hidden features, and a few clarifications. But small wording like this is exactly what most often causes a rejection a team did not expect. Here is what changed and what to check in your app and on your App Store page.
What changed
According to Apple's description, the update covers the following items:
| Item | What is new | Who it affects |
|---|---|---|
| 2.3.14 (new) | A rule on creative assets | Everyone who designs an App Store page |
| 2.5.19 (new) | A ban on hidden, dormant or undocumented features; previously part of 2.3.1 | Everyone, especially teams that test features behind flags |
| 1.2 (changed) | Clarifies which app types and content the user-generated content rule covers | Apps with chats, comments, reviews, feeds |
| 5 (changed) | Apps that facilitate human trafficking or child exploitation are removed and blocked from alternative distribution | Platforms with UGC and communities |
| 3.1.1(a) | The Music Streaming Services Entitlements bullet is removed and merged into StoreKit External Purchase Link Entitlements; links may point to a permitted destination | Apps with external purchase links |
Apple also added links to additional documentation in "Before You Submit" and "After You Submit" and said translations will appear on its website within a month.
2.3.14: creative assets on your app page
The new rule did not appear by chance. On 5 October Apple introduced new creative assets: images and video in product page headers and in search results. Rule 2.3.14 sets the limits for them. According to Apple's text, creative assets:
- must pertain to the app's content and functionality or its overarching brand;
- must follow standard metadata guidelines;
- must be appropriate for all audiences.
They must not include inappropriate content, references to other apps with an intent to mislead, unverifiable product claims, or specific or discounted pricing information. The last point matters for seasonal campaigns: a "50% off today only" banner will not pass as a creative asset. Announce discounts through other means, not in the page visuals.
2.5.19: hidden and undocumented features
This is not a new ban: it used to be part of 2.3.1 and now has its own number. The point is that an app must not contain "hidden, dormant, or undocumented features", and its behavior should be clear to both users and reviewers. Apple adds that trying to hide such features, including through code obfuscation, is grounds for removal of the app and termination of the developer account.
This is not a ban on obfuscation as such: it remains a normal way to protect code. The rule is about hiding what the app does. In practice, check:
- Server-side flags (remote config). If a feature is switched on remotely after review, its existence should be described in the App Review notes;
- Dormant features. Code for future capabilities sitting in the build should either be removed or documented;
- Tester modes and hidden menus. Do not leave them in the production build without an explanation;
- Workaround paths. Anything that changes behavior depending on the country or the reviewer's account is a risk.
In a separate announcement on 16 October Apple explains that 2.5.19 clarifies the long-standing ban on bait-and-switch: an app that misrepresents what it does during review and then adds features that were not in the submitted version after approval. Such apps can be removed from the App Store and the developer removed from the Apple Developer Program.
1.2: user-generated content
Rule 1.2 requires four things from apps that let users create, upload or share content:
- a method for filtering objectionable material;
- a mechanism to report offensive content, with timely responses;
- the ability to block abusive users;
- published contact information.
What is new in the clarification: failing to implement appropriate safeguards, or failing to remediate violations after notice, can be treated as a violation of the Developer Code of Conduct. So the risk is no longer limited to a rejected update; it also reaches the account. In its explanatory announcement Apple explicitly names nonconsensual intimate imagery, including imagery created with AI tools: apps with UGC must proactively prevent and remove it. If you have chats, comments, reviews or communities, check that all four mechanisms really work, not just on paper.
3.1.1(a): external purchase links
The change in 3.1.1(a) is technical: the Music Streaming Services Entitlements bullet is removed and merged into StoreKit External Purchase Link Entitlements. Developers can apply for an entitlement to include a link to a permitted destination for purchasing digital content. Outside specific regions and outside the US storefront, the rules say apps and their metadata may not include buttons, external links or other calls to action that direct customers to purchasing mechanisms other than in-app purchase. If you work with external payments, compare the current rule text with your storefront.
A checklist before your next release
| Area | Question | Action |
|---|---|---|
| Creative assets | Do banners show prices, discounts or comparisons with other apps? | Remove prices and unverifiable claims |
| Features | Does the build contain features the reviewer does not know about? | Describe them in the review notes or remove them |
| Remote config | Does a flag change the essence of the app after review? | Document every such flag |
| UGC | Do filtering, reporting, blocking and contacts work? | Test the flows manually and assign an owner for reports |
| External purchases | Does the link text match the current version of 3.1.1(a)? | Check against the rule for your storefront |
The "Who it affects" column in the first table and this table reflect our practice and interpretation, not Apple's official position. For the full text see the App Review Guidelines.
Conclusion
The October update does not change the rules of the game, but it narrows the room for small violations: prices in creative assets, undocumented flags, weak moderation. These checks fit well into a pre-release checklist, and they cost less than a rejected update in peak season.
Want us to check your app before an App Store submission? Get in touch: we will run a compliance audit and help prepare the page and the reviewer notes.



