Repository navigation
|
How can a team catch Live Activities used for promotional or unsolicited messages automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rn 'ActivityKit\|Activity\.request\|LiveActivity' {S} . # then review every Live Activity for promotional contentRead the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. Guideline 4.5.3 now names Live Activities alongside Game Center and Push Notifications as surfaces that may not be used to spam, phish, or send unsolicited messages. A Live Activity that carries marketing, upsells, or content unrelated to the ongoing activity is rejected. The fix. Keep every Live Activity tied to a real, user-initiated, time-bound activity. No promotions, no engagement bait, no unrelated content in the Dynamic Island or Lock Screen presentation. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
APPLE-4.5.3-LIVE-ACTIVITY-SPAMwith a coverage line and a proper exit code.What the hit means. Guideline 4.5.3 now names Live Activities alongside Game Center and Push Notifications as surfaces that may not be used to spam, phish, or send unsolicited messages. A Live A…