PhilippC / keepass2android

Password manager app for Android
https://play.google.com/store/apps/details?id=keepass2android.keepass2android
GNU General Public License v3.0
4.67k stars 379 forks source link

Fingerprint reader has stopped working #1157

Open ghost opened 4 years ago

ghost commented 4 years ago

Hi,

After the last update the opening database with fingerprint hast stopped working. I have already reinstalled the application, all possible permissions have been granted. I added new fingerprint but the result was the same, opening database with fingerprint did not work.

See details below: Device: Xiaomi Redmi Note 3 Pro (kenzo) OS: MIUI Global Stable 10.2.1.0 MHOMIXM (Android 6) App version: Keepass2Android v1.08-r1

Has anyone experienced these things yet?

Small-Ku commented 4 years ago

There is a note that show up when you try to setup fingerprint:

Also note that Biometric Unlock works by storing your master key in Android's secure storage. This storage may be deleted by Android at any time, e.g. if you add a new fingerprint in the system settings. So don't rely on Biometric Unlock but remember your master password, please!

So, while Android deleted this storage, you will need to unlock the database by your own master password.

ghost commented 4 years ago

Hi Small-Ku,

I understand what you wrote, but the situation is something else. Until the last update I could use the fingerprint unlock, but after the new release (v1.08-r1) it has been stopped working. The unlocking with fingerprint feature was disappeared from the app, at least for me. What should I do to use it again?

Thank you.

PhilippC commented 4 years ago

@pvtpeter can you reenable it if you go to settings - database - biometric unlock?

ghost commented 4 years ago

Hi @PhilippC,

No. I got these errors when I open this menu item: fingerprint_fatal and fingerprint_hardware_error Cannot setup Biometric Unlock: No biometric hardware detected.

I have already reinstalled the application, and deleted the cache and app data. As I said, it was happened when I installed the new update (v1.08-r1) of Keepass2Android. What should I do? Do you have any "debug" version or tool which can identify what is the problem?

Thank you.

ghost commented 4 years ago

@PhilippC: now, I've installed the 1.07b-r0 version, it is working, so there is something anomaly between 1.07b-r0 and v1.08-r1.

PhilippC commented 4 years ago

@pvtpeter I even purchased a Redmi Note3 to test this but unfortunately failed to install Android 6 so far... Note that I am using some Google library for the fingerprint/biometric unlock now. Not sure why it.s not working with this phone.

ghost commented 4 years ago

@PhilippC thank you for your reply. Yes it is interesting. How can I help you hereinafter?

RobMahn commented 4 years ago

When I try to enable Biometric Unlock, I get a Java Runtime Exception. I can't get a screen shot as it's not allowed by the app. The message is only up for a few seconds, but starts with the exception thrown at: keepass2android.BiometricEncryption..init()[0x000aa] in ;0 at keepass2android.BiometricSetupActivity.ChangeUnlockMode(keepass2android.ChangeUnlockModeoldMode,keepass2android.ChangeUnlockModenewMode[0x000b0]

Biometric Unlock used to work for me and I don't know exactly when it stopped. I have a rooted ZTE Axon 7 running a Venom Android 9 version from last October.

I tried clearing date and backing down to 1.08b-r0 with the same results. I backed down to 1.07b-r0 and the app just crashes.

08/28/2020 - I found the cause of the error. After doing a restore, I did not have my lock screen set. My banking app caught this as a requirement and tipped me off.