Closed maxkohne closed 3 years ago
Looks like this is a Google issue:
Hi @maxkohne,
Thanks for bringing this to our attention. We'll look at whether we can avoid this issue altogether or if we have to resort to simply catching and ignoring this SecurityException
. I've filed it internal so we can schedule time to address the issue.
Thanks, @gwhelanLD
It appears this was deprecated in API 28, could this be the culprit? https://developer.android.com/reference/android/net/ConnectivityManager#CONNECTIVITY_ACTION
This exception is causing a large volume of crashes for our users on SDK v3.0.0. When do you anticipate a fix for it ? @gwhelanLD
We are seeing large volumes of this crash too with 3.0.1
. Only happening on Android 11 in the background.
Could you all try this same approach to address?
Closing this issue as it was fixed in the 3.0.2 release.
Thanks, @gwhelanLD
Describe the bug
We are receiving reports of crashes from our crash reporting services. This has been happening since we upgraded to
v3.0.0
of LaunchDarkly. So far, we have only seen reports fromAndroid 11
users and all happen to be on different models of Samsung Galaxy devices (Galaxy A50
,Galaxy A51
,Galaxy A52
,Galaxy S10
, andGalaxy Z Fold2 5G
). All crashes happened in the background according to Crashlytics.To reproduce We cannot reproduce in-house but we are seeing Bugsnag and Crashlytic events for this crash. We do not own any Samsung Galaxy models either.
Expected behavior Don't expect to crash in a background state.
Logs
SDK version v3.0.0
Language version, developer tools Kotlin 1.4.30
OS/platform Android 11