-
Notifications
You must be signed in to change notification settings - Fork 62
No fingerprint enrolled crash #6
Comments
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 then I don't think there's anything I can do in the library to fix this. It's a major issue in the OS. |
@mattprecious glad to hear I'm not the only one experiencing this. While doing some research I found the same bug in the google samples finger print dialog section with multiple people pointing to an emulator problem. From the fabric crash logs though, the same issue/crash is occurring on multiple Samsung and LG devices. |
Bump. Seeing this issue on LG V10. Cant repo, only seen in the crash logs on the play console. |
It's easy to reproduce this on AVD emulators. Problem is that
Exception: Adding new fingerprint solves problem until next emulator reboot. So far I didn't experience this problem on any real device. |
I've tested the no fingerprint enrolled case just recently with a Pixel 2 and the current master (with RxJava 2 support) and it worked without any issues. Given that this issue is quite old should we close this? In case this pops up again one can open up a new one. |
This occurs after restarting one of the default Android emulators. After rebooting the emulator, it still shows a finger print registered. Adding a new one seems to fix the problem, but there seems to be some sort of underlying issue here. We are also seeing the same issue on a few Samsung and LG phones but have been unable reproduce it locally.
The text was updated successfully, but these errors were encountered: