[BUG]

Checks

• I have read the FAQ section, searched the open issues, and still think this is a new bug.

Describe the bug you encountered:

On my Pixel 8 running stock operating system BUT with Microsoft Swiftkey as my default keyboard if I open KP2 Android Offline I immediately get the fingerprint unlock option as I've enabled biometric sign in to my database. This is exactly as expected. When I then select the app I want to sign into I have the option to toggle to KP2 Android keyboard to enter credentials securely

On my partners Samsung A52 with Samsung keyboard as default keyboard again with Biometric sign in activated on KP2 Android when she opens KP2 Android she gets a failure "Fingerprint Operation Cancelled " message and has to dismiss that message select KP2 keyboard then select "Unlock" option in bottom right to get the fingerprint pop up to appear again and only then can she sign in to database with biometrics.

Is this a bug or is there a setting buried somewhere on the Samsung A52 that isn't allowing biometric sign in while the KP2 Android keyboard isn't active?

Thanks

Describe what you expected to happen:

.

What version of Keepass2Android are you using?

Version 1.09e-r7

Which version of Android are you on?

Android 14 UI 6.1

Start by reproducing version 1.09e-r7 on Android 14 UI 6.1 with biometric sign-in enabled, comparing the Pixel 8 with SwiftKey against the Samsung A52 with Samsung Keyboard. Trace the launch flow that produces “Fingerprint Operation Cancelled” before the KP2 keyboard is selected; done means the Samsung setup can reach biometric unlock without dismissing the error or selecting Unlock again.