TooManyRequestException in Library
sulemankhan447 opened this issue · comments
Caused by android.net.ConnectivityManager$TooManyRequestsException
android.net.ConnectivityManager.convertServiceException (ConnectivityManager.java:3609)
android.net.ConnectivityManager.registerDefaultNetworkCallback (ConnectivityManager.java:4256)
com.gojek.networktracker.NetworkStateTrackerImpl.startTracking$network_tracker_release (NetworkStateTrackerImpl.java:115)
com.gojek.networktracker.NetworkStateTrackerImpl.addListener (NetworkStateTrackerImpl.java:86)
com.gojek.keepalive.OptimalKeepAliveCalculator. (OptimalKeepAliveCalculator.java:31)
com.gojek.keepalive.KeepAliveCalculatorFactory.create (KeepAliveCalculatorFactory.java:29)
com.gojek.keepalive.OptimalKeepAliveProvider. (OptimalKeepAliveProvider.java:16)
com.gojek.keepalive.OptimalKeepAliveProvider. (OptimalKeepAliveProvider.java:9)
com.gojek.mqtt.client.internal.MqttClientInternal.initialiseOptimalKeepAliveProvider (MqttClientInternal.java:157)
com.gojek.mqtt.client.internal.MqttClientInternal.initialiseAdaptiveMqttClient (MqttClientInternal.java:122)
com.gojek.mqtt.client.internal.MqttClientInternal. (MqttClientInternal.java:64)
hey @sulemankhan447 can you add more details: Steps to reproduce this issue?
Since android 12, os imposed 100 callback limit. It may be due to some other lib or code path as well. Ref issue: https://issuetracker.google.com/issues/231499040
Courier android lib only registers network callback once per client.
Thanks @anubhav7nov for the reply, unfortunately we are not able to recreate this crash, as per our stack trace its was leading to courier library and we just started receiving this crash after shifting to this library
we will also look into work manager used in our code.
@sulemankhan447 were you able to reproduce the issue or steps to reproduce this issue?
Closing this issue as not reproducible.