age_range_signals 0.4.2
age_range_signals: ^0.4.2 copied to clipboard
Flutter plugin for age verification supporting Google Play Age Signals API (Android) and Apple's Age Range (DeclaredAgeRange) API (iOS 26+).
0.4.2 #
- Android: Fixed
ageLowerandageUpperto read actual values from Google Play Age Signals API- 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=15for a 13-15 age band) - Values are
nullfor verified users (18+) as expected
- Previously these fields were hardcoded to
- iOS: Simplified plugin implementation
- Example App: Added iOS warning explaining that example app cannot run DeclaredAgeRange API without proper entitlement
- Documentation: Updated README to accurately document mock data behavior (returns supervised_13_15 by default, not verified)
0.4.1 #
- Fixed code formatting issues to improve pub.dev score
0.4.0 #
-
Android: Added distinct status values for guardian approval states (#10, thanks to @kumamotone)
AgeSignalsStatus.supervisedApprovalPending- awaiting guardian responseAgeSignalsStatus.supervisedApprovalDenied- guardian denied access
-
iOS: Added regional eligibility check for iOS 26.2+ (#9, thanks to @rokarnus)
- Returns
AgeSignalsStatus.unknownfor users outside applicable regions - Avoids unnecessary API calls when age verification is not available
- Returns
-
Error Handling: Added 6 new exception types with detailed diagnostics
MissingEntitlementException,ApiErrorException,NetworkErrorExceptionUserCancelledException,PlayServicesException,UserNotSignedInException- All exceptions now include a
detailsfield with platform-specific diagnostic information - Enhanced error detection for Play Services, network issues, authentication, and user cancellation
0.3.0 #
-
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.2or higher (previously0.0.1in v0.2.0). Beta versions and0.0.1will 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
- Updated to
-
Migration: No code changes required - just update your dependency version in
pubspec.yaml
0.2.0 #
-
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)
0.1.3 #
- iOS: Fixed compilation error: renamed
range.sourcetorange.ageRangeDeclarationto match Apple's DeclaredAgeRange API (#3)
0.1.2 #
- iOS: Added Swift Package Manager (SPM) support
- Example: Migrated example project from CocoaPods to Swift Package Manager
0.1.1 #
- Android: Add
useMockDataparameter for testing - iOS: Fix critical
requestAgeRangemethod call syntax - iOS: Add support for 1-3 age gates (previously 2-3)
- iOS: Support for Swift Package Manager
- Add pub.dev topics and formatted code for better score
- Documentation improvements and usage examples
0.1.0 #
- Initial release
- Support for Google Play Age Signals API on Android (API 21+)
- Support for Apple's DeclaredAgeRange API on iOS (26.0+)
- Configurable age gates for iOS
- Comprehensive example app with mock data support