Repository navigation
|
How can a team catch Declared Age Range used without handling RESCIND_CONSENT 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 -rqn 'DeclaredAgeRange\|AgeRangeService' . && ! grep -rqn 'RESCIND_CONSENT\|rescindConsent' .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 What the hit means. The app reads Declared Age Range but never handles the RESCIND_CONSENT App Store Server Notification. When a parent withdraws consent Apple prevents the app from launching, and any server-side minor data or entitlement keyed to the withdrawn consent stays live. The fix. Subscribe to App Store Server Notifications, handle RESCIND_CONSENT by revoking the minor's session and deleting consent-scoped data, and build against the iOS 26.2 SDK with Xcode 26.2 (17C52) or later, which Apple requires for all age assurance technologies. 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-5.1.1-RESCIND-CONSENT-UNHANDLEDwith a coverage line and a proper exit code.What the hit means. The app reads Declared Age Range but never handles the RESCIND_CONSENT App Store Server Notification. When a parent withdraws consent Apple prevents the app from launching, and any server-si…