Apple's 2026 App Review Guideline Changes: 4.3(b) Spam, 4.5.3 Live Activities, 1.2 UGC

Quick answer: On June 9, 2026, Apple updated the App Store Review Guidelines. Guideline 4.3(b) now lets Apple reject and even remove apps that are "indistinguishable" from apps already on the store, and it names categories (dating, wallpaper, fortune telling, and more) that must offer a meaningfully different experience. A new Guideline 4.5.3 bans using Live Activities for spam, phishing, or unsolicited messages. A separate February 2026 change pulled random and anonymous chat apps under the user-generated content rule (1.2). Here is what each change means and how to clear review.

Apple revises the App Store Review Guidelines a few times a year. The June 9, 2026 batch matters more than most, because it expands what Apple can do about low-value apps: not just reject a new submission, but remove apps that are already live. For studios and agencies that ship many similar client builds or white-label apps, that turns a one-off rejection into account-level risk.

Below are the three changes that affect the most teams, with the dates, the exact scope, and a checklist to clear review.

What changed in Guideline 4.3(b) on spam?

Guideline 4.3(b) now states that apps which are "indistinguishable from what is already widely available on the App Store" can be rejected. Apple goes further than before in two ways.

First, it names established categories that must provide a "meaningfully different or improved experience" to stay on the store: examples include dating, flashlight, sound effects, wallpaper, simple timers, and fortune telling. Apple says it may remove existing apps in these categories if they are not updated or improved, or if they fail to attract customers.

Second, it calls out a set of low-effort categories by name (drinking games, Kama Sutra, fart, and burp apps) as "mediocre, low-quality, or low-effort." Repeated submissions of this kind can lead to removal from the Apple Developer Program, which affects the whole account, not one app.

Much of 4.3 is a judgment call by the reviewer, so there is no automated pass or fail. What you can control is the technical and metadata hygiene that makes an app look templated: reused bundle structures across many builds, placeholder metadata, identical assets, and near-duplicate binaries. See our existing guide on Guideline 4.3 spam rejections for the patterns reviewers associate with copy-paste apps.

What is the new Guideline 4.5.3 for Live Activities?

Guideline 4.5.3 is new in the June 9, 2026 update. It states that developers may not use Live Activities to send spam, phishing, or unsolicited messages. Live Activities and the broader push-to-start capability became popular through 2025 and 2026 for live scores, deliveries, and ride status. The new rule draws the line: a Live Activity must reflect a real, user-relevant, time-sensitive event, not act as a second notification channel for promotions.

This is a narrow, brand-new rule with very little developer guidance published so far, which makes it both easy to trip over and easy to get right once you know it exists.

What changed for user-generated content (Guideline 1.2)?

In a separate update on February 6, 2026, Apple clarified that apps offering random or anonymous chat fall under the user-generated content guideline (1.2). If your app connects strangers, even briefly, you are expected to have the full UGC control set: a content filter for objectionable material, a mechanism for users to flag content, the ability to block abusive users, and published developer contact information.

Anonymous-chat and "talk to a stranger" apps were a common rejection surprise before this clarification. Now the expectation is explicit.

The 2026 changes at a glance

Guideline	What changed	Effective	What you must do
4.3(b) Spam	Names removable categories; allows removal of existing apps that are not meaningfully different	June 9, 2026	Prove a distinct experience; avoid templated builds and placeholder metadata
4.5.3 Live Activities	Bans Live Activities used for spam, phishing, or unsolicited messages	June 9, 2026	Use Live Activities only for genuine, time-sensitive, user-relevant events
1.2 User-generated content	Random and anonymous chat is explicitly in scope	February 6, 2026	Add filtering, reporting, blocking, and published contact info

How to prepare a build for the 2026 rules (checklist)

1. Confirm the build is compiled with the iOS 26 SDK and Xcode 26 or later. Since April 28, 2026, App Store Connect rejects uploads that are not.
2. For each app in a multi-app or white-label portfolio, verify it has its own distinct functionality, assets, and metadata rather than a shared template.
3. Remove placeholder strings, demo content, and unfinished screens that read as "low effort" to a reviewer.
4. Audit every Live Activity: confirm it is tied to a real event the user opted into, and that it never carries promotional or unsolicited content.
5. If the app has any chat, matching, or stranger-connection feature, ship the full UGC control set and document it in the review notes.
6. Check that your App Store metadata (screenshots, description, keywords) matches what the binary actually does.

Where a pre-submission check helps

Most 4.3 decisions are subjective, and no tool can promise a reviewer's verdict. What a pre-submission scan of the compiled binary and its metadata can do is surface the technical signals that get apps flagged: duplicate structures across a portfolio, placeholder metadata, and declared capabilities that the binary does not back up. Finding those in CI is cheaper than finding them in a rejection email. For the broader pre-flight, see our iOS app submission checklist.

Frequently asked questions

Can Apple remove an app that was already approved under 4.3(b)?

Yes. The June 9, 2026 update explicitly allows Apple to remove existing apps in the named categories (such as dating, wallpaper, and fortune telling) if they are not meaningfully different or improved, or if they fail to attract customers. This is a change from treating 4.3 as a submission-time check only.

Does Guideline 4.5.3 ban all Live Activities?

No. It bans using Live Activities for spam, phishing, or unsolicited messages. Legitimate, time-sensitive Live Activities (live scores, deliveries, transit, ride status) remain fully allowed.

Is the iOS 26 SDK required for new submissions?

Yes. Since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26 SDK. Your deployment target can still support older iOS versions.

My app has anonymous chat. What do I need before submitting?

Under the February 2026 clarification of Guideline 1.2, you need a content filter, a way for users to report objectionable content, a way to block abusive users, and published developer contact information.