Matthew Precious
Matthew Precious
I just looked into the details of the events and batching looks insanely hard.
Maybe someone else will figure it out!
Do we need to bring back `awaitFrame()` for these tests?
The repro in the sample does throw the same exception, but that's intentional since it calls `read()` twice which would trigger the underlying Android bug.
Ah, yeah. You are correct.
Ugh... that bug is the worst. Does the lockscreen register its listener before your `onPause()` is called? > Repro steps (can use latest version of Robinhood to repro): :flag-ca:
@alan-rodriguez, are you getting another `onResume()` call once the lock screen is unlocked?
Alright, that's interesting. I was worried that `onResume` wasn't getting called another time after the phone was unlocked, which would prevent your app from starting up the fingerprint reader at...
I've been trying to reproduce this crash on Samsung for months... I'll try restarting the phone a bunch of times and see if it'll repro. If this is the cause...
This is probably a bug in the sample app. It should probably cancel the fingerprint authentication when the activity is paused.