PhilippC / PhilippC/keepass2android
[BUG] Fingerprint always failing on first run
Nobody has claimed this yet.
- 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:
Fingerprint authentication is always failing when started the first time, but can be restarted manually then and authenticating successfully
Describe what you expected to happen:
After migration from Xiaomi MIUI 14 (Android 13) to HyperOS 1 (Android 14) I have a new issue:
Every fresh start, the fingerprint authentication is failing. I get a short fingerprint screen, then just a toast message:
"Fingerabdruckverarbeitung fehlgeschlagen"
and the usual password unlock dialog. I can then press on the fingerprint button again to start the fingerprint-auth, and this time it works.
What version of Keepass2Android are you using?
1.11-r0
Which version of Android are you on?
14
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
No source file, test, or entry point is identified in the issue. Reproduce the first-run failure on Android 14 with Keepass2Android 1.11-r0, compare it with the successful second attempt, and define done as first-launch fingerprint authentication succeeding without a manual restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100