You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Question: on which Android versions is it needed and not needed? #15
@AndroidDeveloperLB I could only tell you that recently I've seen in Crashlytics an issue with AlertDialog that was giving an error of BadTokenException. It happened on Samsung and Xiaomi devices with Android 9.
The project is built with pre-AndroidX components with targetSdkVersion 28.
I don't know either on which exactly Android versions and devices it happens.
You mean that it can occur on Android 9, right?
Do you know the cause of it in Android code? Maybe this way you can compare between what you know in Android 9 and 10.
I don't think it matters about android-x.
It's a toast. Plus it gets converted anyway to android-x.
And seeing that you used only the annotations of the support library, you can convert to Kotlin and not use anything of the support library (and android-x).
Yes, it seems it can occur because it has occured on Android 9. As I saw in Crashlytics of app deployed on Google Store.
I know only that it happened when the app was trying to call the show() method on the AlertDialog object. Unfortunately, nothing more.
I cannot reproduce the error in my Environment (Android 9 and 10 emulators and Samsung's smartphones with Android 5 and 6). I am just giving you (and maybe others) information that the issue happened. So, just in case you could also handle exceptions on the Android 9 version.
The eyes emoji means that I am also looking for the answer to your question.
Activity
danielgalion commentedon Feb 13, 2020
@AndroidDeveloperLB I could only tell you that recently I've seen in Crashlytics an issue with AlertDialog that was giving an error of BadTokenException. It happened on Samsung and Xiaomi devices with Android 9.
The project is built with pre-AndroidX components with targetSdkVersion 28.
I don't know either on which exactly Android versions and devices it happens.
AndroidDeveloperLB commentedon Feb 13, 2020
You mean that it can occur on Android 9, right?
Do you know the cause of it in Android code? Maybe this way you can compare between what you know in Android 9 and 10.
I don't think it matters about android-x.
It's a toast. Plus it gets converted anyway to android-x.
And seeing that you used only the annotations of the support library, you can convert to Kotlin and not use anything of the support library (and android-x).
BTW, what's with the eyes emoji?
danielgalion commentedon Feb 13, 2020
Yes, it seems it can occur because it has occured on Android 9. As I saw in Crashlytics of app deployed on Google Store.
I know only that it happened when the app was trying to call the show() method on the AlertDialog object. Unfortunately, nothing more.
I cannot reproduce the error in my Environment (Android 9 and 10 emulators and Samsung's smartphones with Android 5 and 6). I am just giving you (and maybe others) information that the issue happened. So, just in case you could also handle exceptions on the Android 9 version.
The eyes emoji means that I am also looking for the answer to your question.
AndroidDeveloperLB commentedon Feb 14, 2020
How come it happens anyway? Is Google aware of the issue? Is there a report here?
It occurs only for Samsung and Xiaomi devices?