The library appears to be initializing correctly; however, we are encountering an issue when requesting the user's age range. Although the AgeSignalsService is expected to be operational in Brazil as of March 2026, the Logcat indicates a failure in identifying a valid account flavor, which seems to prevent the correct retrieval of age signals.
The onCompleteCheckAgeSignals callback is triggered, and the controller returns success, but the underlying Play Services/Finsky logs suggest the signal is not being processed as expected and always returning "null".
2026-05-12 16:30:23.128 17873-17906 Finsky:background com.android.vending:background W [69] AV::AgeSignalsServiceImpl: No accounts with known API flavor found.
2026-05-12 16:30:23.128 17873-17911 Finsky:background com.android.vending:background I [74] Device is eligible for platform Cronet and will attempt to use it.
2026-05-12 16:30:23.128 17873-17920 ConnectivityManager com.android.vending:background D StackLog: [android.net.ConnectivityManager.sendRequestForNetwork(ConnectivityManager.java:4740)] [android.net.ConnectivityManager.registerDefaultNetworkCallbackForUid(ConnectivityManager.java:5465)] [android.net.ConnectivityManager.registerDefaultNetworkCallback(ConnectivityManager.java:5432)] [android.net.ConnectivityManager.registerDefaultNetworkCallback(ConnectivityManager.java:5406)] [acfo.call(PG:27)] [bmvi.a(PG:3)] [bmun.run(PG:19)] [bmvj.run(PG:5)] [java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1154)] [java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:652)] [upg.run(PG:65)] [java.lang.Thread.run(Thread.java:1564)]
2026-05-12 16:30:23.129 14341-14682 PlayCore air.br.com.megajogos.mobile I UID: [10416] PID: [14341] OnCheckAgeSignalsCallback : onCompleteCheckAgeSignals
2026-05-12 16:30:23.129 14341-14341 com.distriqt.AgeRange air.br.com.megajogos.mobile D AgeSignalsController::requestAgeRange() - success
The library appears to be initializing correctly; however, we are encountering an issue when requesting the user's age range. Although the AgeSignalsService is expected to be operational in Brazil as of March 2026, the Logcat indicates a failure in identifying a valid account flavor, which seems to prevent the correct retrieval of age signals.