PhilippC / PhilippC/keepass2android

[BUG] Biometric Login gets removed whenever using Keepass within a new app

Open
#2,937 23 comments 6 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:

I'm using Keepass2Android on my phone now for a long time, but this behaviour is new and starting to get annoying.

I assume it's something in the background changed how android is handling authentication.

What's happening:
You install an app on the phone you already have the login data inside keepass, or you want to store the credentials in keepass.
When Android shows the prompt to open up keepass on the keyboard, you select it and the biometric login pops up. But it will always fail, you don't have any chance of trying it again and you need to enter the password and activate biometric unlock again.

From the behaviour it feels like, biometric login must be enabled again from every app calling Keepass and it gets stored somewhere. If I would just minimize the app, open keepass manually and copy the data or create a new entry, that's working. But after calling it from an unknown app, biometric login gets disabled.

Describe what you expected to happen:

Biometric login should work, once it has been configured, without the need to do it over and over again.

What version of Keepass2Android are you using?

1.12-r5

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 by reproducing the Android 16 flow from an app invoking Keepass2Android through the keyboard, then compare it with opening Keepass2Android directly. Check where the biometric prompt fails and where biometric unlock is disabled or re-enabled. Done means biometric login continues to work after the external app flow without manual password entry or reactivation.

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.