-
Notifications
You must be signed in to change notification settings - Fork 851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitwarden crashing on biometric unlock #4659
Comments
Thank you for your report! We've added this to our internal board for review. |
I have the same problem. Here is my crash log |
I can confirm. Same issue on Samsung Galaxy S24 Ultra with latest oneui 7 beta 3. |
Thanks everyone for providing all the details and logs. This has been passed to our Engineering team |
I have a similar issue, as soon as i add a second account and enable "Unlock with Biometrics" for it. Steps to reproduce
ResultTry to unlock "Account-A" with my fingerprint = crash
As soon as i remove "Unlock with Biometrics" from one account and reconfigure it for the other one, it works (for that specific account). Build Version2025.1.1 (19728) (Play Store) Environment Details
|
Issue still present at 2025.1.2. Partial Workarround:
In any case, issue returns when active account changes. |
Can recreate what @kslcsdalsadg said. Issue is temporarily fixed if I login using master password and re-enable unlock using biometrics, and this works. However, for users with two accounts (like me), it's causing issues. |
On my Samsung Galaxy S22 the issue also occurs with only one account. Re-enabling doesn't fix it. Crashes on fingerprint unlock.
|
So, why is this closed? Unfortunately I've got the same problem. |
|
Same here, have the same problem, with the exact behavior as described by @ohaucke |
I am also experiencing the same issue, and I have the latest version from Google Play installed. Why is this BUG closed? Or better yet, when will this fix be available? |
Pull request #4696 is supposed to resolve this issue. I assume it was closed for this reason. |
I believe you are right, ignore my request to reopen this issue. I assumed this PR was in the last release (mainly because it was released after the PR was merged). It is NOT. So for anyone reading this, please wait for the next release. |
Looking forward to the next update with the fix |
Fix finally included in release 2025.2.0
|
Just tried 2025.2.0 On my Samsung galaxy S22, it is not fixed on my side. The app still crashes on biometric unlock. (It now also crashes when enabling biometrics after disabling)
Could this be re-opened please ? |
This is happening to me on 2025.2.0 only in my work profile bitwarden when trying to enable biometrics. I'm on GrapheneOS and used shelter to clone the app over to my work profile. Here is the log: crash
|
I've just tested it on my OnePlus 11 5G ( First i added biometric login for the second account (first account already had it actived) - works without any isssues |
Tested with Pixel 8, Android 15, Bitwarden 2025.2.0 (current on gplay) |
Thank you for providing crash details, @phoropter. We've identified the cause of the crash and hope to have a fix in the next release. I'll go ahead and re-open this issue for visibility. |
Steps To Reproduce
Expected Result
My vault should unlock.
Actual Result
The app is crashing.
Screenshots or Videos
No response
Additional Context
Might be similar to 4651 & 4650 perhaps?
Anyway, here's a logcat I captured about the crash as well:
FATAL EXCEPTION: main Process: com.x8bit.bitwarden, PID: 20692 javax.crypto.BadPaddingException at android.security.keystore2.AndroidKeyStoreCipherSpiBase.engineDoFinal(AndroidKeyStoreCipherSpiBase.java:630) at javax.crypto.Cipher.doFinal(Cipher.java:2074) at a8.A0.R(Unknown Source:113) at J8.O.invokeSuspend(Unknown Source:43) at Jb.a.resumeWith(Unknown Source:7) at ec.K.run(Unknown Source:109) at ec.X.d0(Unknown Source:23) at ec.l.o(Unknown Source:80) at ec.l.s(Unknown Source:2) at gc.l.a(Unknown Source:6) at gc.j.I(Unknown Source:84) at gc.j.g(Unknown Source:56) at gc.j.p(Unknown Source:107) at Q8.d.i(Unknown Source:2) at J8.x.invoke(Unknown Source:116) at S8.d.invoke(Unknown Source:11) at ma.b.F(Unknown Source:15) at c.o.run(Unknown Source:246) at android.os.Handler.handleCallback(Handler.java:959) at android.os.Handler.dispatchMessage(Handler.java:100) at android.os.Looper.loopOnce(Looper.java:282) at android.os.Looper.loop(Looper.java:387) at android.app.ActivityThread.main(ActivityThread.java:9505) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:600) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1005) Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [t0{Cancelling}@9b8c38, Dispatchers.Main.immediate] Caused by: android.security.KeyStoreException: Invalid argument (internal Keystore code: -38 message: system/security/keystore2/src/operation.rs:847: KeystoreOperation::finish Caused by: 0: system/security/keystore2/src/operation.rs:428: Finish failed. 1: Error::Km(r#INVALID_ARGUMENT)) (public error code: 10 internal Keystore code: -38) at android.security.KeyStore2.getKeyStoreException(KeyStore2.java:416) at android.security.KeyStoreOperation.handleExceptions(KeyStoreOperation.java:79) at android.security.KeyStoreOperation.finish(KeyStoreOperation.java:132) at android.security.keystore2.KeyStoreCryptoOperationChunkedStreamer$MainDataStream.finish(KeyStoreCryptoOperationChunkedStreamer.java:228) at android.security.keystore2.KeyStoreCryptoOperationChunkedStreamer.doFinal(KeyStoreCryptoOperationChunkedStreamer.java:181) at android.security.keystore2.AndroidKeyStoreCipherSpiBase.engineDoFinal(AndroidKeyStoreCipherSpiBase.java:624) ... 25 more
Build Version
2025.1.1 (Play Store)
What server are you connecting to?
US
Self-host Server Version
No response
Environment Details
Issue Tracking Info
The text was updated successfully, but these errors were encountered: