Open ytheekshana opened 5 years ago
hmmm, it's a bug. fortunately, or unfortunately, it occurs just under android M: https://issuetracker.google.com/issues/37061719
they announced one or two workaround(s). it's not fit for me. but i tried to avoid it at the next commit. see my commit later.
And, there is another way to disable the exception: DON'T enable displayPath
in your case. That means: call .displayPath(false)
.
if you like displayPath, retrieve the patch (8d6156f6d2, or 5257025c2d) by following jitpack doc:
Ok. I'll call .displayPath(false) as I don't need the path displayed. Thanks
hmm, I've been testing it on a Kitkat emulator, yet I am failing to replicate this exception
hmm, I've been testing it on a Kitkat emulator, yet I am failing to replicate this exception
Happened to me only on Android 6
fortunately, or unfortunately, it occurs just under android M
thought any api < 26? I'll check M then
edit: indeed, I got the error...
the patch is a work around for M, and the operating expirences has not been break. i guess that's ok now.
there is a simpler way to make it work though:
if (_alertDialog != null && _alertDialog.isShowing() && _displayPath) { ...
just need to check that _alertDialog is already showing.
1.1.19 out, please confirm that the problem has been solved.
omarman_2006a@hotmail.com
Is that issue is resolved? If yes then how?
Got a runtime exception only on Android 6 devices after 1.1.17 update