age_range_signals 0.5.0

age_range_signals: ^0.5.0 copied to clipboard

Android: Added mockData parameter for customizable testing

• New AgeSignalsMockData class allows testing different scenarios
• Uses Google's official FakeAgeSignalsManager from com.google.android.play.agesignals.testing package
• Can customize status, age ranges, and installId for testing
• Defaults to supervised user (13-15) for backward compatibility with existing tests

Documentation: Major updates and improvements

• Added Texas SB 2420 federal court injunction notice (December 23, 2025)
• Comprehensive testing documentation for both platforms
• Clarified that mockData is Android-only (iOS has no official testing utilities from Apple)
• Updated README with accurate testing requirements and platform-specific limitations
• Improved example app comments to explain platform differences

iOS: No changes

• Continues to ignore useMockData and mockData parameters (same as 0.4.2)
• Apple does not provide testing utilities for DeclaredAgeRange API
• iOS testing requires real iOS 26.2+ devices with actual Apple IDs

• Previously these fields were hardcoded to null, now they correctly return age range values for supervised users
• Age ranges are returned as integer bounds (e.g., ageLower=13, ageUpper=15 for a 13-15 age band)
• Values are null for verified users (18+) as expected

Android: Added distinct status values for guardian approval states (#10, thanks to @kumamotone)

• AgeSignalsStatus.supervisedApprovalPending - awaiting guardian response
• AgeSignalsStatus.supervisedApprovalDenied - guardian denied access

iOS: Added regional eligibility check for iOS 26.2+ (#9, thanks to @rokarnus)

• Returns AgeSignalsStatus.unknown for users outside applicable regions
• Avoids unnecessary API calls when age verification is not available

Error Handling: Added 6 new exception types with detailed diagnostics

• MissingEntitlementException, ApiErrorException, NetworkErrorException
• UserCancelledException, PlayServicesException, UserNotSignedInException
• All exceptions now include a details field with platform-specific diagnostic information
• Enhanced error detection for Play Services, network issues, authentication, and user cancellation

IMPORTANT: Critical update to ensure compatibility with Google Play Age Signals API requirements (effective January 1, 2026)

Android: ⚠️ Google has updated their requirements again - the Play Age Signals API now requires version 0.0.2 or higher (previously 0.0.1 in v0.2.0). Beta versions and 0.0.1 will throw exceptions starting January 1, 2026. (thanks to @JenniO for reporting this in #7)

• Updated to com.google.android.play:age-signals:0.0.2 (latest required version)
• Updated build tools to match Flutter's official plugins for improved compatibility and future-proofing

Migration: No code changes required - just update your dependency version in pubspec.yaml

Android: ⚠️ CRITICAL UPDATE - Bumped Play Age Signals API library version to non-beta stable release com.google.android.play:age-signals:0.0.1 (thanks to @rokarnus for reporting this in #5)

ACTION REQUIRED: Users must upgrade to version 0.2.0 or higher before January 1, 2026

• Why: From January 1, 2026, all beta versions (0.0.1-beta*) of the Play Age Signals API will throw exceptions
• Impact: Apps using older versions of this plugin (with beta API) will stop working after January 1, 2026
• To receive live responses from January 1, 2026, you must upgrade to this library version (0.2.0 or higher)