Fixed
Status Update
Comments
jo...@google.com <jo...@google.com> #2
Note: crash happens right after installation. No user interaction is needed, just installing APK.
je...@google.com <je...@google.com> #3
Observation: crash happens also with new app built from Android Studio template.
Maybe it's happening only on Cyanogenmod/LineageOS ROMs... I'm not sure.
Maybe it's happening only on Cyanogenmod/LineageOS ROMs... I'm not sure.
ap...@google.com <ap...@google.com> #4
Are all the crashes you see only happening only on Cyanogenmod? I am unable to reproduce it.
pr...@google.com <pr...@google.com> #5
I see "Android Vitals" and "ANRs and crashes", then screens like in attachments. So Google developer console tells me about crashes, but I don't see details of device ROM or such. But amount of these crashes is huge.
From direct user emails I could setup one configuration where it crashes for me - Cyanogenmod 12.1 on i9250
I can't tell if it's on other OEM ROMs.
Even if it was just on Cyanogenmod/LineageOS, I think it's not for ignoration, userbase of these ROMs is large.
Try to grab Samsung i9250, install CM12.1 on it, and you'll reproduce it.
From direct user emails I could setup one configuration where it crashes for me - Cyanogenmod 12.1 on i9250
I can't tell if it's on other OEM ROMs.
Even if it was just on Cyanogenmod/LineageOS, I think it's not for ignoration, userbase of these ROMs is large.
Try to grab Samsung i9250, install CM12.1 on it, and you'll reproduce it.
Description
When the down and the up event arrive in rapid succession, it is possible that the onPress callback is executed after the onTap callback.
It is currently not possible to reproduce this in a test, because we use an
UnconfinedTestDispatcher
. When we switch to aStandardTestDispatcher
, the following test (when added toTapGestureDetectorTest.kt
) will fail:While very difficult, I think you could reproduce it in a demo app with an incredibly short tap.