Closed goodevilgenius closed 1 month ago
Additional information: this seems to only happen if biometric unlocking is enabled, even if it hasn't been set for a particular file.
Also, I mistakenly believed this was only in the latest version, because it was a recent change. However, I tried downgrading and the issue persisted, until I cleared app data and didn't enable biometric unlocking.
So, it seems to be related to a change in that, rather than the app specifically.
This is not a KeePassDX update regression. The problem has been reported on some Samsung devices (specifically on S10). The Keystore on these devices doesn't seem to be handled properly, try to delete a biometric fingerprint and put it back.
Duplicate https://github.com/Kunzisoft/KeePassDX/issues/1269 https://github.com/Kunzisoft/KeePassDX/issues/1269#issuecomment-1075449893
The Keystore on these devices doesn't seem to be handled properly, try to delete a biometric fingerprint and put it back.
Interesting. Thanks for this. I wonder what changed recently that this suddenly became an issue for me when I've been using it for years without problem.
I'll give this a try.
Try to delete a biometric fingerprint and put it back.
Thanks for the suggestion. Unfortunately, that didn't help at all. I tried deleting all my fingerprints, and then putting them back in. Once I re-enabled biometrics in KeepassDX settings, it freezes up.
Bummer that Samsung screwed this up, and I can't use it anymore.
Maybe a reboot is the solution? https://github.com/Kunzisoft/KeePassDX/issues/1269#issuecomment-1115339395
Maybe a reboot is the solution?
Of course that's it. 😆
Thank you. Working with fingerprint again. If it stops working again in six months, I guess I'll know what to do.
**Describe the bug**
Starting with the newest version, attempting to open a file causes the app to freeze when entering password.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should be able to enter password (or read fingerprint)
KeePass Database
KeePassDX:
Android:
Additional context
Add any other context about the problem here.
Saw behavior both with using auto fill, and opening app directly.
Also cleared app data and created new file, and still saw this bug.