-
-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Biometric unlock broken #1150
Comments
Hi, Thanks for the detailed report. Cheers |
After doing that, the app is completely broken. I cannot even start it, it completely crashes with the following SQLite error which repeats upon every app start.
|
Had to uninstall the app, reinstall and restore from backup. Lost all the settings. Upon fresh install, app works without SQLite or biometric unlock issues. Could be caused by version upgrade but it is definitely not user-friendly or smooth experience. @jamie-mh I'll leave it up to you to close this if you do not want to investigate. |
It works for me using 1.25.1. OS: One UI 6.0, based of Android 14 (Samsung) |
For the sake of helping this issue, I tried it on my Android 11 based custom OS. However, I just installed this app and didn't add any entries yet. Maybe some older update broke something earlier, which becomes only visible in rare scenarios? At least, the following strongly suggests, this is the case.
Maybe add a warning to an FAQ or the README, so people are aware of such an issue, when upgrading from older versions? 🙂 |
Describe the bug
Biometric unlock on 1.25.1 does not work. On app startup, I always have to log in using password. When I head to settings and try to enable BU there, modal with fingerprint scan pops up and I can scan my finger. Then the pill button briefly shows BU enabled but then immediately switches back to disabled BU state.
To Reproduce
Steps to reproduce the behavior:
Error
Failed to store cipher
appears in log:Expected behavior
Working BU.
App Version
1.25.1, Android 11, OnePlus 7Pro
Additional context
Full log attached.
12_06-19-54-39_102.log
The text was updated successfully, but these errors were encountered: