PhilippC / PhilippC/keepass2android
[BUG] Biometric unlock of database lose key file config
Nobody has claimed this yet.
- #2901 by @PhilippC — closed without merging
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
Checks
- I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:
Since the last 1.12-r5 version installed from the beta program on play store, when I enable biometric full unlock for my database the app sometime forget to use the key file and the fingerprint unlock then fails.
I then have to select again the key file and enter my password.
I'm on a Pixel 7 with Android 15.
Describe what you expected to happen:
No response
What version of Keepass2Android are you using?
1.12-r5
Which version of Android are you on?
15
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the biometric full-unlock flow with a database that uses a key file on Android 15 and version 1.12-r5. Review closed pull request #2901 and its discussion for prior investigation; the issue is done when biometric unlock reliably retains and uses the selected key file without requiring it to be selected again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- authentication, mobile, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100