PhilippC / PhilippC/keepass2android

[BUG] Fingerprint scanner not working on Pixel 10 Pro

Open
#3,114 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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:

When I tried to open the database with quick access, I got a toast message that the Fingerprint was not available. I then have to use the last three characters of my password. When I press the Fingerprint button in the app instead of typing the characters I get a popup with an error saying (partially dutch):
"Ontgrendelen met biometrie

Error initializing Fingerprint Unlock:

System.Exception: Failed to init cipher for fingerprint Init: key is null

at keepass2android. BiometricDecryption.Init() at keepass2android.QuickUnlock.InitFingerpri ntUnlock()"

Describe what you expected to happen:

I would expect to be able to use my fingerprint to quickly unlock my database.

What version of Keepass2Android are you using?

1.14-r4

Which version of Android are you on?

16

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with QuickUnlock.InitFingerprintUnlock() and BiometricDecryption.Init(), using the reported “key is null” stack trace as the entry point. Reproduce on Android 16 with a Pixel 10 Pro and version 1.14-r4, then trace fingerprint initialization. Done means fingerprint quick unlock initializes successfully instead of falling back to password characters.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.