[BUG] Prime ignoring touch inputs occasionally
Version: 2.29.2
Device: Samsung Galaxy S10e
OS: Android 9
Summary
So, since @RedSoloCup urged me to post the "Prime ignoring touch inputs occasionally" issue here, here we go.
Video 1: https://www.youtube.com/watch?v=YoEeV4V5dag - Map View
Here we can see Prime in Map View. Testing methodology: I tap on 4 spots on the map repeatedly, ripple is registered touch in the app, missing ripple (mostly the last one in the row) means no touch registered. This gets apparent at the end of the video.
Video 2: https://www.youtube.com/watch?v=6rbr8IUVLmI - Inventory Scrolling
Scrolling in inventory screen. It repeatedly trips over itself.
Video 3: https://www.youtube.com/watch?v=QNWkSXXlhWU - Key selection in "Manage"
Every now and then, keys just don't get selected even though they get tapped. With multiple test runs at 24 keys, 3 keys always got ignored. It's apparent that from the Android system side, the touch did happen and it still didn't get selected.
Video 4: https://www.youtube.com/watch?v=tpliHBvDkz0 - Key Scrolling
Similar to inventory view, scrolling trips over itself, especially at fast swipes, or the inertia doesn't fit. Sometimes swipes don't even register.
Comments
Pixel 2XL, running 2.29.2, Android 9
I can replicate 1 and 3, but for me it's the second tap that isn't registered most of the time.
2 and 4 I can not replicate, scrolling is always triggered regardless of how fast I try
Mi A1, Mi8 Android 9 - can't reproduce it.
2.31.2, still Samsung Galaxy S10e, Android 9 - it got slightly worse.
The weird thing is, I have recordings of other agents that don't experience this, ever.
What's going on?
I think it got worse with the latest version of Ingress Prime. See https://www.instagram.com/p/B2fIkmOobww
At this point the client was completely unusable. This is prime 2.31.2 on a one plus 7 pro...
Touch issues in key manage. Meaning you can Touch a key but it doesnt get selected are present also in 2.31.2
this is in the google spreadsheet that niantic has not updated in forever.
it is related to the time length of the tap. a quick tap of short duration will register. a slower tap of a longer duration will not.
this is easiest to see on the key list, but can also be seen in other places.
i've pointed it out to @redsolocup but i doubt he remembers.
this is the last serious usability issue i have with prime.