Fingerprint Unlock keeps getting disabled.


I'm having an issue that after enabling a Fingerprint unlock on a DB, after a while it gets disabled. I then have to enter the password manually and enabled fingerprint unlock again in the Database Settings.
Could this be caused by my Tasker profile which removes Pin lock when I connect to specific Wifi networks (using Secure Settings).
I'm not sure if that is the cause because I tested the profile multiple times and the Fingerprint didn't get lost and even when the Pin lock is removed, the fingerprints are still there (in Android Settings/Security)..

Is there a way for me to troubleshoot this? Anyway to get a log file?


jepho wrote Oct 3, 2016 at 10:43 AM

This is so true. Seeing this behaviour on Marshmallow 6.0.1.

Spikelangelo wrote Oct 14, 2016 at 5:18 PM

It worked without issues for a while, then a few weeks ago I noticed the same thing, randomly disabled fingerprint. It's happening quite regularly now, possibly related to rebooting (at least in my case.)

databoy2k wrote Feb 15 at 11:21 AM

I hate to necro an old bug, but this is definitely back as of the 1.01 changes. I'm getting it every time on my Galaxy S7 (7.0) and Galaxy Tab S (6.0.1). Quickunlock opens, but it seems like it gives up on a fingerprint before you even have a chance to provide your fingerprint.

If I recall correctly, it was around the 0.97 that this same bug existed and was squashed and it seems to be back.

mlamers wrote Feb 26 at 4:05 PM

I have the same behavior on my Galaxy S7.
I thought this is a Samsung problem as other apps struggle to get it right also.
1Paassword for example has the exact same problem on my device whereas other apps like "Banking 4A" work.