Play Age Signals release notes

This page explains what's in the recent updates to the Maven repository for the Play Age Signals Library.

0.0.4 (July 2026)

• Two-function architecture: Starting with this release, you must use the following methods to receive age signals:
  • requestAgeSignalsAccess() (new method): Explicitly triggers the Play in-app prompt for age range sharing request.
  • checkAgeSignals() (existing method): Receive age signals.
• Deprecate userStatus: userStatus is deprecated and no longer supported in version 0.0.4 or higher. userStatus is now replaced by ageRangeSource and significantChangeStatus.
• New field for significant changes: Introduced the significantChangeStatus enum field to track pending, approved, or declined status for significant changes, and renamed mostRecentApprovalDate to significantChangeApprovalDate for clarity.

0.0.3 (February 2026)

• Add user status DECLARED.
• Add error code SDK_VERSION_OUTDATED.
• Fix unit test failures when calling the AgeSignalsResult builder.

0.0.2 (December 2025)

• This release makes sure empty values are returned as null.
• This release of the library will return real results when the API is enabled.

0.0.1 (December 2025)

• The first non-beta release of the library will return real results when the API is enabled.

0.0.1-beta02 (October 2025)

• Add FakeAgeSignalsManager, a fake implementation of the AgeSignalsManager.
• Replace com.google.type.Date by java.util.Date.
• This release won't return real results when the API is enabled.

0.0.1-beta01 (October 2025)

• Initial release.
• This release won't return real results when the API is enabled.