Expo AgeRange

Returns the set of regulatory features that the OS reports as required for the current user.

Use this to discover which age-assurance obligations apply.

Resolves with null on iOS earlier than 26.4 and on Android and web — treat null as "unknown" rather than "no features required".

Asks the OS whether age-assurance regulation applies to the current user. Apple uses this to signal that the account region is covered by a law such as Utah's or Louisiana's age-assurance requirements, so apps can avoid gating users in jurisdictions where the rules do not apply.

• Resolves with true only when Apple confirms regulation applies.
• Resolves with false when the OS confirms regulation does not apply.
• Resolves with null on iOS earlier than 26.2, and on Android and web. Treat null as "unknown" rather than a definitive false.
• Rejects when the request fails — see AgeRangeService.Error for more information. Treat rejection as "unknown" and fall through to requestAgeRangeAsync or your own gating logic.

Recommended pattern: call this first and only prompt the user for their age range when the result is not false. When it is false, the user is outside a regulated jurisdiction and you can skip the age gate entirely.

try {
  const eligible = await isEligibleForAgeFeaturesAsync();
  if (eligible === false) {
    // Regulation does not apply — no age gate needed.
    return;
  }
} catch {
  // Treat errors as "unknown" and fall through to the prompt below or your own gating logic.
}

const ageRange = await requestAgeRangeAsync({ threshold1: 18 });

Prompts the user to share their age range with the app. Responses may be cached by the OS for future requests.

Asks the user to consent to sharing their age signals, showing the Play Age Signals in-app age sharing consent screen. Play Age Signals requires this before requestAgeRangeAsync: age signals are only reported while the status is 'SHARED'.

• Resolves with 'SHARED' when the user agrees to share their age signals. Only then does requestAgeRangeAsync report an age range.
• Resolves with 'NOT_SHARED' when the user does not agree. requestAgeRangeAsync reports every field as null until the user consents.
• Resolves with 'VERIFICATION_REQUIRED' when the user's age is unknown and they are in a region where age verification is mandatory. Ask the user to visit the Play Store to resolve their status.
• Resolves with null when Play Age Signals reports no status, and on iOS and web. On iOS the consent prompt is part of requestAgeRangeAsync itself, so there is nothing separate to call.
• Rejects when the request fails.

Fakes the age signals that requestAgeRangeAsync and requestAgeSignalsAccessAsync report, using Play Age Signals FakeAgeSignalsManager. Pass null to go back to the real signals.

Only debuggable builds can fake signals. Passing anything other than null in a build that is not debuggable throws.

// A supervised 13 to 15 year old with a change waiting for approval.
setFakeAgeSignals({
  ageSignalsStatus: 'SHARED',
  lowerBound: 13,
  upperBound: 15,
  ageRangeSource: 'TIER_B',
  significantChangeStatus: 'PENDING',
});

Displays a system-provided interface for people to acknowledge a significant app update.

Only on iOS 26.4+, this presents an update acknowledgement dialog and resolves once the user confirms it, or rejects with an error. On unsupported platforms this resolves immediately without showing any UI.

Call getRequiredRegulatoryFeaturesAsync first to determine whether the user actually needs to acknowledge a significant change — only invoke this function when the returned features include 'significantAppChangeRequiresAdultNotification'. Doing so avoids prompting users who are not subject to the regulation.