PhilippC / PhilippC/keepass2android

[BUG] Error Initializing Biometric Unlock

Open
#2,615 11 comments 1 reaction 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:

Encountered error on trying to use fingerprint to open file. New phone (Pixel 8). Transfered apps. Copied kdbx. Opened with password. Opted for fingerprint opening. Got error (see below) fingerprint works with all other apps.

Describe what you expected to happen:

Tried to open with fingerprint. Got error:
Biometric unlock
Error initializing Fingerprint Unlock: System.Exception: Failed to init cipher for fingerprint Init: key is null at keepass 2android.BiometricDecryp tion.Init [Ox00080] in <dabeaecbf9c 0465bb1 ce8a7bcc561 766>:0
at keepass2android. QuickUnlock.I
nitFingerprintUnlock (0 [Ox000fa] in <dabeaecbf9c0465bb1 ce8a 7bcc5617 66>:0

What version of Keepass2Android are you using?

1.10-pre

Which version of Android are you on?

14

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 by reproducing the fingerprint-unlock failure on Android 14 with Keepass2Android 1.10-pre, using the reported Pixel 8 and transferred kdbx setup. Trace the reported BiometricDecryption.Init and QuickUnlock.InitFingerprintUnlock entry points, then verify that fingerprint unlock initializes successfully and opens the copied file without the key-null error.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, csharp
Domain
authentication, mobile-dev, 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.