onError() called immediately for RxReprint.authenticate() if previous scan failed about reprint HOT 3 CLOSED

What device are you using? What is the FailureReason returned in onError?

I'll look into this in more detail, but on first glance it's obvious that you shouldn't restart the activity like this. It's possible that is causing the issue. If you want to retry fatal errors, you should write your own action to pass to retry. Keep in mind that a fatal error means that the fingerprint scanner is unavailable or has locked you out, so restarting will return an error immediately in that case.

from reprint.

The android emulator.

On Aug 9, 2016 17:53, "AJ Alt" [email protected] wrote:

What device are you using?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ajalt/reprint/issues/15#issuecomment-238716982, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAlGe-gYiCZRy1rbZtPDBBx5D1NWbiZbks5qeQTagaJpZM4Jgb7R
.

from reprint.

First off, thanks for the code to reproduce the issue. It's really helpful.

So what's happening is that the system is locking the sensor due to too many failed authentication attempts. Nexus devices usually do that after five failures, and lock the sensor for 30 seconds or so. Samsung devices so all sorts of stuff, including disabling the sensor indefinitely until the user types in their password.

If the sensor is locked or unavailable, onError will get called immediately, and there's nothing that can be done about it. The authentication is not tied to an Activity, so restarting won't unlock the sensor.

Let me know if you still have questions.

from reprint.