search

PhilippC / keepass2android

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

Biometric access error #1622

Open giopluk opened 3 years ago

giopluk commented 3 years ago

When I try to set up biometric access, I have the error message in screenshot. Someone else solved the problem? Screenshot_20210325-062258

knoelli commented 3 years ago

I do have exactly the same error message when setting up biometric access on the latest beta 1.09a-pre1. However, biometric access used to work just fine up to (and including) version 1.08d-r5, so for me this is an issue with the latest update.

giopluk commented 3 years ago

Thanks for the answer. I have 1.08d-r5 version on phone, an Asus ZenFone 3 (ze520kl), probably it's a compatibility problem

Il dom 28 mar 2021, 12:07 knoelli @.***> ha scritto:

I do have exactly the same error message when setting up biometric access on the latest beta 1.09a-pre1. However, biometric access used to work just fine up to (and including) version 1.08d-r5, so for me this is an issue with the latest update.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/PhilippC/keepass2android/issues/1622#issuecomment-808875021, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATMT6IGN3DNR7QD5HRPPHHDTF4EVHANCNFSM4ZYU3YBA .

knoelli commented 3 years ago

I just tried the latest version (1.09a-r1) and the problem still persists.

After the upgrade, I was able to unlock the database with my fingerprint, so saved biometric credentials seem to work just fine.

However, when trying to add a fingerprint to unlock (by first disabling biometric unlocking and then activating it again in the database settings), I get the above mentioned error and cannot unlock the database anymore with a fingerprint from this point on.

Reverting back to 1.08d-r5 fixed the problem (again) for me.

PhilippC commented 3 years ago

@knoelli I can't reproduce what you describe. Can you provide a log (see app settings) and details about which device you are using.

knoelli commented 2 years ago

@PhilippC Sorry for the late reply, your answer has somehow slipped my attention. I was just about to create a logfile using the latest version 1.09a-r3 but this new release fixes the above mentioned problem for me. If it is of use to you, I could downgrade to 1.09a-r1 and create a logfile with that version, but probably that's no longer needed?!