PhilippC
[BUG] Biometric Login gets removed whenever using Keepass within a new app
Checks
- [x] 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
I have the same problem on my Moto G85 5G, with Keepass 1.12-r5 on Android 15. But my wife doesn't have the issue with the same Keepass version but on Android 13 (Moto G62 5G).
I have the same problem on my Moto Razr 50 Ultra. And it's very VERY annoying to enter my long password on a touchscreen keyboard so many times. I was just starting to search for an alternative to this wonderful app just because of that, but I said, lets try to see if the issue was posted here.
This is 100% an actual bug which wasn't present before the update to the latest Android available for my phone (Android 15 here).
Cheers!
I have tried many things and still cannot reproduce it which makes it very hard to solve.
Can anybody reproduce this on an Android emulator? If so, you can tell me how exactly you created that and describe the steps to reproduce there. That could be a way of making it reproducible for me as well.
I'm not sure if this has something to do with the keyboard settings, or how google is detecting to provide, when keepass should be opened. My girlfriend has a pixel 9 and I tried to reproduce it, as she asked what this issue is, while seeing im getting github mails ^^
I installed a new app on her phone and navigated to the login section, I think we tried netflix or disney+, but she didn't get the popup to open or search in keepass. And it's only happening while using these.
If I minimize and open keepass from the usual shortcut, everything works as intended, it's only happening while keepass is opened inside the calling app, or how ever this is working :)
I don't have an Android emulator, but if it helps, the problem only shows up when Keepass is starting and the fingerprint is required instead of the full password. The fingerprint always works (for me) when the alternative would be the quick unlock.
I think I understood what you describe, but feel free to provide a video to make sure I'm doing exactly the same thing that you do.
@Gille2k did you check that the two devices were running the same version?
So I just tried again with the ebay app. If I install it fresh on my phone, open ebay, click on login with email adress and click into the email field, the keeboard is offering me "fill with keepass" If I click it, keepass will be called within the app and it will lead to the above error.
Same steps on my girlfriends phone, the "fill with keepass" option is not popping up. So she need to go the usual way, minimize ebay and just open up keepass. I checked the versions I'm on Android 16 June 5th, she is on July 5th, we both use gboard as our main keyboard.
I tried with a new application on my other phone, a Samsung S23FE, which also has Android 15 but with OneUI7, and the bug doesn't reproduce there... Seems that what I have in common with @Gille2k is that we both have a Motorola phone. What we have in common with others (Graphene OS and Pxiel 9A) is the fact that all of them have almost stock Android...
Upsi, sorry, I mixed your answear with @cmd-at-home respose
I installed a new app on her phone and navigated to the login section, I think we tried netflix or disney+, but she didn't get the popup to open or search in keepass. And it's only happening while using these.
@Gille2k long press the form and click autofill. It should then propose you to autocomplete with k2a.
@PhilippC when this happens, in recent apps overview there is no K2A because it loads inside the application that requested it.
I found out, why it's not popping up on my girl friends phone, in the Keepass up the Auto Fill Service is not active, and I couldn't convince her, to let me play a bit more with the phone, to do some tests ^^
Hi there, I struggle with the same problem since weeks on my S24 with android 15 and OneUI 7, always using the latest KeePass version. But I'm not sure if the above descriptions completely describe the phenomenon. For me it looks like I have to open KeePass first, directly, before using in autotifill. If I haven't used KeePass for a while, and then start an autofill in any app, the fingerprint reader for KeePass is popping up. But after reading the fingerprint, KeePass doesn't procede. Instead the login screen from KeePass is shown and asking for password. After entering password the biometric detection dialog pops up.
@PhilippC If that would help, we might meet and I show you on my device. Maybe making a local debug session
@hcrutz are you located close to Karlsruhe, Germany? If so, we could do so!
Once again to anybody here: Can you setup any emulator (using Android developer tools) and reproduce the issue there? I'd be more than happy to fix this, but with all my devices, this simply doesn't happen.
I have a log file from the occurrence of the problem, after a number of successful Quick unlocks. Would that be useful? It's about 124kB in size.
From: PhilippC @.> Sent: Tuesday, August 12, 2025 10:16:23 AM To: PhilippC/keepass2android @.> Cc: cmd-at-home @.>; Mention @.> Subject: Re: [PhilippC/keepass2android] [BUG] Biometric Login gets removed whenever using Keepass within a new app (Issue #2937)
[https://avatars.githubusercontent.com/u/5421734?s=20&v=4]PhilippC left a comment (PhilippC/keepass2android#2937)https://github.com/PhilippC/keepass2android/issues/2937#issuecomment-3178475374
Once again to anybody here: Can you setup any emulator (using Android developer tools) and reproduce the issue there? I'd be more than happy to fix this, but with all my devices, this simply doesn't happen.
— Reply to this email directly, view it on GitHubhttps://github.com/PhilippC/keepass2android/issues/2937#issuecomment-3178475374, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BUT7EYBQWFWMCCQOGGMF4GL3NGWGPAVCNFSM6AAAAACBALXVCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZYGQ3TKMZXGQ. You are receiving this because you were mentioned.Message ID: @.***>
feel free to post it here or to [email protected] and I will have a look, but I'm 99% sure I need a device/emulator where this happens so I can test why. (The log only shows "what" happens)
Can you suggest a suitable emulator, either for Win 11 or Ubuntu 22.04?
Chris
Chris Dorling @.***> 07961 108743
From: PhilippC @.> Sent: 19 August 2025 10:53 To: PhilippC/keepass2android @.> Cc: cmd-at-home @.>; Mention @.> Subject: Re: [PhilippC/keepass2android] [BUG] Biometric Login gets removed whenever using Keepass within a new app (Issue #2937)
[https://avatars.githubusercontent.com/u/5421734?s=20&v=4]PhilippC left a comment (PhilippC/keepass2android#2937)https://github.com/PhilippC/keepass2android/issues/2937#issuecomment-3200052617
feel free to post it here or to @.@.> and I will have a look, but I'm 99% sure I need a device/emulator where this happens so I can test why. (The log only shows "what" happens)
— Reply to this email directly, view it on GitHubhttps://github.com/PhilippC/keepass2android/issues/2937#issuecomment-3200052617, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BUT7EYCVFNRDFRCSKN5Z5J33OLX2VAVCNFSM6AAAAACBALXVCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMBQGA2TENRRG4. You are receiving this because you were mentioned.Message ID: @.***>
you can setup emulators from Android Studio (https://developer.android.com/studio) in Tools / Device Manager.
Note that it looks like you have a phone number in your mail signature which shows up here on Github.
reportedly this is solved in v1.12-r6b (https://github.com/PhilippC/keepass2android/issues/2869)
@PhilippC maybe this version has not yet been fully pushed / rolled out by Google Play, at least I did not receive it yet. So people keep reporting it because they don't have the version with the fix.
I can confirm, installing that apk (mentioned here specifically: https://github.com/PhilippC/keepass2android/issues/2869#issuecomment-2982314579) seems to have resolved the problem as originally described in this issue, from which I too was suffering on my Galaxy ZFold6.
