Android: Don't show dialog while TooManyAttempts error is active about xamarin-fingerprint

[smsissuechecker]

Hi @nielscup,

I'm the friendly issue checker.
Thanks for using the issue template 🌟
I appreciate it very much. I'm sure, the maintainers of this repository will answer, soon.

[smstuebe]

Is it the same with the default dialog?

[nielscup]

When using the default dialog the dialog is always shown. So only the custom dialog does not show on a non-Samsung device. Any way to have this behaviour on a Samsung device as well? I have looked through the code but it wasn't very obvious how to fix this. Maybe if you can point me in the right direction I can have another look. Thanks!

[smstuebe]

Device	Default Dialog	Custom Dialog
Samsung	shows normally	disappears immediately (wrong behavior)
Other	shows normally	shows normally

correct?

[nielscup]

Not exactly: I would like the dialog not to popup at all while TooManyAttempts is active. I would like to receive the TooManyAttempts message from AuthenticateAsync while it is active, without showing a popup. Just like the title of this issue says: Don't show dialog while TooManyAttempts error is active. I get this (correct) behaviour on non-Samsung devices, but not on a Samsung. Samsung always pops up the dialog shortly if you can't use fingerprint because it is blocked.

[TheSayvior]

Hello, I'm exspriencing what is think is the same issue on android in my Xamarin project on my Nexus 5.
Once i have gotten the TooManyAttempts error then it saves that error untill it have been evaluated a sekund time or enough time has passed. This behavior does not show/happen on my iOS device.

Sorry for messing up the formular but since its already here i think I'll just supply what i think is different @smsissuechecker :)

Configuration
Version of the Plugin: 1.4.7
Platform: Android 8.1.0
Device: Nexus 5

Exspected behavior:
When i start a new
result = await CrossFingerprint.AuthenticateAsync(new AuthenticationRequestConfiguration());
after having had the result status of TooMany Attempts prior to starting a new, then it waits for me to use my finger and does not reuse the same result from last time the Authendication was called and evaluated to TooManyAttempts.

Actual behavior:
When the Authendication has evaluated to tooManyAttempts, the device remembers this for a duration of time and will throw that result again instantly next time I call the authendication havent gotten the time but its +5-10 sekunds that the device or plugin remembers the result status of tooManyAttempts.

[smstuebe]

lifecycle is now completely managed by biometric prompt