Recommendations for building a permission priming experience around DeclaredAgeRange TCC

Unlike almost all other system TCC prompts, the DeclaredAgeRange does not have an API to detect the current status.

This makes it hard to determine when it is appropriate to show a permission flow that explains what the app does with the information.

I do the workflow during onboarding, and when app features are being accessed. I would like to not just 'pop up' if the user completed onboarding on iOS 18, and then upgraded to 26 (or 27).

FB21157742

Currently, DeclaredAgeRange does not provide a status API but it uses caching mechanism to ensure the user is not prompted for onboarding or to share their age range if the request is for the same exact age gates or if the user has previously onboarded.

Recommendations for building a permission priming experience around DeclaredAgeRange TCC
 
 
Q