[GH-ISSUE #1191] App immediately crashes after unlocking vault #840

New issue

Closed

opened 2026-03-03 02:03:48 +03:00 by kerem · 18 comments

kerem commented 2026-03-03 02:03:48 +03:00

Owner

Copy link

Originally created by @reydus on GitHub (Oct 19, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1191

Subject of the issue

When unlocking the vault, once you have logged in, you type your master password, and after hitting the button, it immediately crashes.

This is very similar if not identical to issue #1169, however it didn't get solved after updating both the app and the server.

Your environment

• Bitwarden_rs version: 1.17 (latest as of 19/10/2020)
• Install method: Docker
• Clients used: Bitwarden from the Play Store, on Samsung's One UI 2.0 (Android 10)
• NGINX reverse proxy
• postgres

Steps to reproduce

Log in as normal
Lock the vault
Input the CORRECT master password and hit button.

Expected behaviour

The main screen with the vault content shows up.
*If a wrong password is inserted, it will say wrong password.

Actual behaviour

it immediately crashes (it goes to home screen for me, no messages)

Relevant logs

Here's a adb logcat:

10-19 00:14:17.606 24415 24415 I MonoDroid: System.Exception: PBKDF2 iteration minimum is 5000.
10-19 00:14:17.606 24415 24415 I MonoDroid:   at Bit.Core.Services.CryptoService.MakeKeyAsync (System.String password, System.String salt, System.Nullable`1[T] kdf, System.Nullable`1[T] kdfIterations) [0x00087] in <6dfd726fecb34ba79c31a035ec98a215>:0
10-19 00:14:17.606 24415 24415 I MonoDroid:   at Bit.App.Pages.LockPageViewModel.SubmitAsync () [0x0078a] in <0c3398d4c9ce4e56ba576728f942d695>:0
10-19 00:14:17.606 24415 24415 I MonoDroid:   at Bit.App.Pages.LockPage.<Unlock_Clicked>b__17_1 () [0x00067] in <0c3398d4c9ce4e56ba576728f942d695>:0
10-19 00:14:17.606 24415 24415 I MonoDroid:   at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__7_0 (System.Object state) [0x00000] in <8f1a893b5ab6478299d5fb8196347666>:0
10-19 00:14:17.606 24415 24415 I MonoDroid:   at Android.App.SyncContext+<>c__DisplayClass2_0.<Post>b__0 () [0x00000] in <3b6b09cca6ad40039584e80046fcd050>:0
10-19 00:14:17.606 24415 24415 I MonoDroid:   at Java.Lang.Thread+RunnableImplementor.Run () [0x00008] in <3b6b09cca6ad40039584e80046fcd050>:0
10-19 00:14:17.606 24415 24415 I MonoDroid:   at Java.Lang.IRunnableInvoker.n_Run (System.IntPtr jnienv, System.IntPtr native__this) [0x00008] in <3b6b09cca6ad40039584e80046fcd050>:0
10-19 00:14:17.606 24415 24415 I MonoDroid:   at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.51(intptr,intptr)
10-19 00:14:17.617  4183  4183 I Layer   : id=18180[1] Destroyed InputMethod$_2387#0
10-19 00:14:17.667 24415 24415 D AndroidRuntime: Shutting down VM
10-19 00:14:17.668 24415 24415 E AndroidRuntime: FATAL EXCEPTION: main
10-19 00:14:17.668 24415 24415 E AndroidRuntime: Process: com.x8bit.bitwarden, PID: 24415
10-19 00:14:17.668 24415 24415 E AndroidRuntime: android.runtime.JavaProxyThrowable: System.Exception: PBKDF2 iteration minimum is 5000.
10-19 00:14:17.668 24415 24415 E AndroidRuntime:   at Bit.Core.Services.CryptoService.MakeKeyAsync (System.String password, System.String salt, System.Nullable`1[T] kdf, System.Nullable`1[T] kdfIterations) [0x00087] in <6dfd726fecb34ba79c31a035ec98a215>:0
10-19 00:14:17.668 24415 24415 E AndroidRuntime:   at Bit.App.Pages.LockPageViewModel.SubmitAsync () [0x0078a] in <0c3398d4c9ce4e56ba576728f942d695>:0
10-19 00:14:17.668 24415 24415 E AndroidRuntime:   at Bit.App.Pages.LockPage.<Unlock_Clicked>b__17_1 () [0x00067] in <0c3398d4c9ce4e56ba576728f942d695>:0
10-19 00:14:17.668 24415 24415 E AndroidRuntime:   at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__7_0 (System.Object state) [0x00000] in <8f1a893b5ab6478299d5fb8196347666>:0
10-19 00:14:17.668 24415 24415 E AndroidRuntime:   at Android.App.SyncContext+<>c__DisplayClass2_0.<Post>b__0 () [0x00000] in <3b6b09cca6ad40039584e80046fcd050>:0
10-19 00:14:17.668 24415 24415 E AndroidRuntime:   at Java.Lang.Thread+RunnableImplementor.Run () [0x00008] in <3b6b09cca6ad40039584e80046fcd050>:0
10-19 00:14:17.668 24415 24415 E AndroidRuntime:   at Java.Lang.IRunnableInvoker.n_Run (System.IntPtr jnienv, System.IntPtr native__this) [0x00008] in <3b6b09cca6ad40039584e80046fcd050>:0
10-19 00:14:17.668 24415 24415 E AndroidRuntime:   at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.51(intptr,intptr)
10-19 00:14:17.668 24415 24415 E AndroidRuntime:        at mono.java.lang.RunnableImplementor.n_run(Native Method)
10-19 00:14:17.668 24415 24415 E AndroidRuntime:        at mono.java.lang.RunnableImplementor.run(RunnableImplementor.java:30)
10-19 00:14:17.668 24415 24415 E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:883)
10-19 00:14:17.668 24415 24415 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:100)
10-19 00:14:17.668 24415 24415 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:237)
10-19 00:14:17.668 24415 24415 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:7814)
10-19 00:14:17.668 24415 24415 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
10-19 00:14:17.668 24415 24415 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
10-19 00:14:17.668 24415 24415 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1075)
10-19 00:14:17.688  4716 24623 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2

Originally created by @reydus on GitHub (Oct 19, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1191 <!-- # ### NOTE: Please update to the latest version of bitwarden_rs before reporting an issue! This saves you and us a lot of time and troubleshooting. See: https://github.com/dani-garcia/bitwarden_rs/issues/1180 # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/obfuscate personal and confidential information, such as names, global IP/DNS addresses and especially passwords, if necessary. --> ### Subject of the issue <!-- Describe your issue here.--> When unlocking the vault, once you have logged in, you type your master password, and after hitting the button, it immediately crashes. This is very similar if not identical to issue #1169, however it didn't get solved after updating both the app and the server. ### Your environment - Bitwarden_rs version: 1.17 (latest as of 19/10/2020) - Install method: Docker - Clients used: Bitwarden from the Play Store, on Samsung's One UI 2.0 (Android 10) - NGINX reverse proxy - postgres ### Steps to reproduce Log in as normal Lock the vault Input the CORRECT master password and hit button. ### Expected behaviour The main screen with the vault content shows up. *If a wrong password is inserted, it will say wrong password. ### Actual behaviour it immediately crashes (it goes to home screen for me, no messages) ### Relevant logs Here's a adb logcat: ``` 10-19 00:14:17.606 24415 24415 I MonoDroid: System.Exception: PBKDF2 iteration minimum is 5000. 10-19 00:14:17.606 24415 24415 I MonoDroid: at Bit.Core.Services.CryptoService.MakeKeyAsync (System.String password, System.String salt, System.Nullable`1[T] kdf, System.Nullable`1[T] kdfIterations) [0x00087] in <6dfd726fecb34ba79c31a035ec98a215>:0 10-19 00:14:17.606 24415 24415 I MonoDroid: at Bit.App.Pages.LockPageViewModel.SubmitAsync () [0x0078a] in <0c3398d4c9ce4e56ba576728f942d695>:0 10-19 00:14:17.606 24415 24415 I MonoDroid: at Bit.App.Pages.LockPage.<Unlock_Clicked>b__17_1 () [0x00067] in <0c3398d4c9ce4e56ba576728f942d695>:0 10-19 00:14:17.606 24415 24415 I MonoDroid: at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__7_0 (System.Object state) [0x00000] in <8f1a893b5ab6478299d5fb8196347666>:0 10-19 00:14:17.606 24415 24415 I MonoDroid: at Android.App.SyncContext+<>c__DisplayClass2_0.<Post>b__0 () [0x00000] in <3b6b09cca6ad40039584e80046fcd050>:0 10-19 00:14:17.606 24415 24415 I MonoDroid: at Java.Lang.Thread+RunnableImplementor.Run () [0x00008] in <3b6b09cca6ad40039584e80046fcd050>:0 10-19 00:14:17.606 24415 24415 I MonoDroid: at Java.Lang.IRunnableInvoker.n_Run (System.IntPtr jnienv, System.IntPtr native__this) [0x00008] in <3b6b09cca6ad40039584e80046fcd050>:0 10-19 00:14:17.606 24415 24415 I MonoDroid: at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.51(intptr,intptr) 10-19 00:14:17.617 4183 4183 I Layer : id=18180[1] Destroyed InputMethod$_2387#0 10-19 00:14:17.667 24415 24415 D AndroidRuntime: Shutting down VM 10-19 00:14:17.668 24415 24415 E AndroidRuntime: FATAL EXCEPTION: main 10-19 00:14:17.668 24415 24415 E AndroidRuntime: Process: com.x8bit.bitwarden, PID: 24415 10-19 00:14:17.668 24415 24415 E AndroidRuntime: android.runtime.JavaProxyThrowable: System.Exception: PBKDF2 iteration minimum is 5000. 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at Bit.Core.Services.CryptoService.MakeKeyAsync (System.String password, System.String salt, System.Nullable`1[T] kdf, System.Nullable`1[T] kdfIterations) [0x00087] in <6dfd726fecb34ba79c31a035ec98a215>:0 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at Bit.App.Pages.LockPageViewModel.SubmitAsync () [0x0078a] in <0c3398d4c9ce4e56ba576728f942d695>:0 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at Bit.App.Pages.LockPage.<Unlock_Clicked>b__17_1 () [0x00067] in <0c3398d4c9ce4e56ba576728f942d695>:0 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__7_0 (System.Object state) [0x00000] in <8f1a893b5ab6478299d5fb8196347666>:0 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at Android.App.SyncContext+<>c__DisplayClass2_0.<Post>b__0 () [0x00000] in <3b6b09cca6ad40039584e80046fcd050>:0 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at Java.Lang.Thread+RunnableImplementor.Run () [0x00008] in <3b6b09cca6ad40039584e80046fcd050>:0 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at Java.Lang.IRunnableInvoker.n_Run (System.IntPtr jnienv, System.IntPtr native__this) [0x00008] in <3b6b09cca6ad40039584e80046fcd050>:0 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.51(intptr,intptr) 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at mono.java.lang.RunnableImplementor.n_run(Native Method) 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at mono.java.lang.RunnableImplementor.run(RunnableImplementor.java:30) 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883) 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100) 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at android.os.Looper.loop(Looper.java:237) 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7814) 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493) 10-19 00:14:17.668 24415 24415 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1075) 10-19 00:14:17.688 4716 24623 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2 ```

kerem 2026-03-03 02:03:48 +03:00

• closed this issue
• added the
  question
  better for forum
  labels

kerem commented 2026-03-03 02:03:49 +03:00

Author

Owner

Copy link

@v-willems commented on GitHub (Oct 19, 2020):

On the latest raspberry pi version, I had the same issue, but with every client. I updated to latest, which fixed it with each client (Chrome-, Safari-extensions, MacOS App, iOS-App) but the android one. Surprisingly, biometrical (re-)login works just fine.
As a workaround, you might want to use this method for now.

<!-- gh-comment-id:712258055 --> @v-willems commented on GitHub (Oct 19, 2020): On the latest raspberry pi version, I had the same issue, but with every client. I updated to latest, which fixed it with each client (Chrome-, Safari-extensions, MacOS App, iOS-App) but the android one. Surprisingly, biometrical (re-)login works just fine. As a workaround, you might want to use this method for now.

kerem commented 2026-03-03 02:03:49 +03:00

Author

Owner

Copy link

@reydus commented on GitHub (Oct 20, 2020):

I built from source the original bitwarden mobile repo to see if I could debug it and find a line or something. But the error did not happen in this version. I will compare both the built and the Play Store version.

<!-- gh-comment-id:713011773 --> @reydus commented on GitHub (Oct 20, 2020): I built from source the original [bitwarden mobile repo](https://github.com/bitwarden/mobile) to see if I could debug it and find a line or something. But the error did not happen in this version. I will compare both the built and the Play Store version.

kerem commented 2026-03-03 02:03:49 +03:00

Author

Owner

Copy link

@nextlogic-ono commented on GitHub (Oct 22, 2020):

You have to logout and login again than just retyping password which is slightly inconvenient but can avoid the crash for now.

Fingerprint unlocking works fine though.

<!-- gh-comment-id:714424516 --> @nextlogic-ono commented on GitHub (Oct 22, 2020): You have to logout and login again than just retyping password which is slightly inconvenient but can avoid the crash for now. Fingerprint unlocking works fine though.

kerem commented 2026-03-03 02:03:49 +03:00

Author

Owner

Copy link

@BlackDex commented on GitHub (Oct 22, 2020):

Which version of the android client are you using?

<!-- gh-comment-id:714433006 --> @BlackDex commented on GitHub (Oct 22, 2020): Which version of the android client are you using?

kerem commented 2026-03-03 02:03:49 +03:00

Author

Owner

Copy link

@nextlogic-ono commented on GitHub (Oct 23, 2020):

I'm using the newest client at the moment which is 2.6.1 (3178).
This happened on both Pixel 4a (Android 11) and Galaxy S10 (Android 10).
I've pulled the bitwardenrs/server:latest image now but it's still happening.

<!-- gh-comment-id:714891509 --> @nextlogic-ono commented on GitHub (Oct 23, 2020): I'm using the newest client at the moment which is `2.6.1 (3178)`. This happened on both Pixel 4a (Android 11) and Galaxy S10 (Android 10). I've pulled the `bitwardenrs/server:latest` image now but it's still happening.

kerem commented 2026-03-03 02:03:49 +03:00

Author

Owner

Copy link

@nextlogic-ono commented on GitHub (Oct 23, 2020):

This is also happening on macOS (10.15.7).

I'm using Edge 86.0.622.48 with the official Bitwarden extension version 1.46.2 which are both the newest versions at this point.

Whenever the vault gets locked and it used to unlock fine by just typing the password but now I have to logout and login again as it says "Invalid master password", though I'm typing in the right one but it's not crashing anything for macOS.

<!-- gh-comment-id:714891754 --> @nextlogic-ono commented on GitHub (Oct 23, 2020): This is also happening on macOS (10.15.7). I'm using `Edge 86.0.622.48` with the official Bitwarden extension version `1.46.2` which are both the newest versions at this point. Whenever the vault gets locked and it used to unlock fine by just typing the password but now I have to logout and login again as it says "Invalid master password", though I'm typing in the right one but it's not crashing anything for macOS.

kerem commented 2026-03-03 02:03:49 +03:00

Author

Owner

Copy link

@BlackDex commented on GitHub (Oct 23, 2020):

@windware-ono, how did you install bitwarden? Plain docker or docker compose? Did you also restart your reverse proxy after the update.
Can you also please verify via the admin interface that the right version is installed?

I'm using the android version 3226, which is a bit newer and i can't reproduce this at all.

Also, what do you see in your logs? What request is coming in at bitwarden.

<!-- gh-comment-id:714936610 --> @BlackDex commented on GitHub (Oct 23, 2020): @windware-ono, how did you install bitwarden? Plain docker or docker compose? Did you also restart your reverse proxy after the update. Can you also please verify via the admin interface that the right version is installed? I'm using the android version 3226, which is a bit newer and i can't reproduce this at all. Also, what do you see in your logs? What request is coming in at bitwarden.

kerem commented 2026-03-03 02:03:49 +03:00

Author

Owner

Copy link

@potvinp commented on GitHub (Oct 24, 2020):

I'm currently having this same issue with the Bitwarden mobile app on iOS 14.0.1. Server and web versions are up-to-date (1.17.0 for server and 2.16.1 for web) according to the /admin/diagnostics page, and the date and time matches as well. Installed via docker-compose. When running the docker pull bitwardenrs/server:latest command, Docker says that the image is up-to-date. The Bitwarden mobile app on my iPhone XS is running version 2.6.1, which appears to be the latest version on the App Store.

When logging in via the mobile app, the following entry shows up in the server's logs:

[2020-10-24 20:22:16.778][rustls::msgs::handshake][WARN] Illegal SNI hostname received [50, 48, 57, 46, 49, 52, 49, 46, 52, 50, 46, 49, 56, 55]

I'm unsure if this is an issue caused by the server or the client, but I can login without issues in Google Chrome with the extension running on MacOS and on Windows.

<!-- gh-comment-id:716050650 --> @potvinp commented on GitHub (Oct 24, 2020): I'm currently having this same issue with the Bitwarden mobile app on iOS 14.0.1. Server and web versions are up-to-date (1.17.0 for server and 2.16.1 for web) according to the /admin/diagnostics page, and the date and time matches as well. Installed via docker-compose. When running the `docker pull bitwardenrs/server:latest` command, Docker says that the image is up-to-date. The Bitwarden mobile app on my iPhone XS is running version 2.6.1, which appears to be the latest version on the App Store. When logging in via the mobile app, the following entry shows up in the server's logs: `[2020-10-24 20:22:16.778][rustls::msgs::handshake][WARN] Illegal SNI hostname received [50, 48, 57, 46, 49, 52, 49, 46, 52, 50, 46, 49, 56, 55]` I'm unsure if this is an issue caused by the server or the client, but I can login without issues in Google Chrome with the extension running on MacOS and on Windows.

kerem commented 2026-03-03 02:03:49 +03:00

Author

Owner

Copy link

@nextlogic-ono commented on GitHub (Oct 27, 2020):

@windware-ono, how did you install bitwarden? Plain docker or docker compose? Did you also restart your reverse proxy after the update.

I installed it via docker-compose.
I haven't changed the reverse proxy's setting but I just restarted it but no change.

Can you also please verify via the admin interface that the right version is installed?

Where do I find the bitwarden_rs version? I saw it says 2.14.0 in the footer, but I assume this is actual Bitwarden's version that's being used.

I'm using the android version 3226, which is a bit newer and i can't reproduce this at all.

I can't see any newer version than 2.6.1 at the Play Store, so I'm at 3178.

Also, what do you see in your logs? What request is coming in at bitwarden.

Say, I have the Android Bitwarden app at the unlocked state, and if I go to Lock Now in the settings, it locks me out and if I type in the password to unlock, it crashes but the server doesn't see any new logs.
If I logout and login again using the password, the server sees new log entries and it succeeds. Like said above, using the fingerprint to unlock after locking works fine but no new logs at the server for this as well.

It's the same for macOS, except the browser extension doesn't have fingerprint unlock feature.

So, it does sound like it's the client's problem when it crashes without contacting the server but I don't have knowledge of the internal working mechanism to be sure.

<!-- gh-comment-id:717418602 --> @nextlogic-ono commented on GitHub (Oct 27, 2020): > @windware-ono, how did you install bitwarden? Plain docker or docker compose? Did you also restart your reverse proxy after the update. I installed it via docker-compose. I haven't changed the reverse proxy's setting but I just restarted it but no change. > Can you also please verify via the admin interface that the right version is installed? Where do I find the bitwarden_rs version? I saw it says `2.14.0` in the footer, but I assume this is actual Bitwarden's version that's being used. > I'm using the android version 3226, which is a bit newer and i can't reproduce this at all. I can't see any newer version than 2.6.1 at the Play Store, so I'm at 3178. > Also, what do you see in your logs? What request is coming in at bitwarden. Say, I have the Android Bitwarden app at the unlocked state, and if I go to `Lock Now` in the settings, it locks me out and if I type in the password to unlock, it crashes but the server doesn't see any new logs. If I logout and login again using the password, the server sees new log entries and it succeeds. Like said above, using the fingerprint to unlock after locking works fine but no new logs at the server for this as well. It's the same for macOS, except the browser extension doesn't have fingerprint unlock feature. So, it does sound like it's the client's problem when it crashes without contacting the server but I don't have knowledge of the internal working mechanism to be sure.

kerem commented 2026-03-03 02:03:49 +03:00

Author

Owner

Copy link

@Office-Monkey commented on GitHub (Oct 28, 2020):

I was afflicted by this for the last few days on Android. I was able to workaround it by: updating my server build (it was overdue) AND clearing both cache and data for the application (uninstall/reinstall might also work?). Hope this might help someone else.

<!-- gh-comment-id:717752156 --> @Office-Monkey commented on GitHub (Oct 28, 2020): I was afflicted by this for the last few days on Android. I was able to workaround it by: updating my server build (it was overdue) AND clearing both cache and data for the application (uninstall/reinstall might also work?). Hope this might help someone else.

kerem commented 2026-03-03 02:03:50 +03:00

Author

Owner

Copy link

@BlackDex commented on GitHub (Nov 18, 2020):

@reydus were you able to solve this issue using the provided comments and updating your server and maybe by clearing the cache of the mobile application?

<!-- gh-comment-id:729627630 --> @BlackDex commented on GitHub (Nov 18, 2020): @reydus were you able to solve this issue using the provided comments and updating your server and maybe by clearing the cache of the mobile application?

kerem commented 2026-03-03 02:03:50 +03:00

Author

Owner

Copy link

@nwallace commented on GitHub (Dec 2, 2020):

I had the same issue happening on iOS. Turns out I had some bad data other clients handled fine, but the phone didn't. In my case, I had a Login URI whose URI was null.

To find the borked data, I whipped up a Ruby script to help:

$ cat << EOF > /tmp/find_nulls.rb
#! /usr/bin/env ruby

require 'json'

def find_nulls(item, path=[])
  case item
  when Hash
    item.each do |k, v|
      find_nulls(v, path + [k])
    end
  when Array
    item.each_with_index do |v, i|
      find_nulls(v, path + [i])
    end
  when NilClass
    puts path.join(".")
  end
end

find_nulls(JSON.parse(STDIN.read))
EOF

$ chmod +x /tmp/find_nulls.rb
$ bw list items | /tmp/find_nulls.rb

You can scan the output manually to find fields that don't sound like they should be null, or use various other tools to help out. I did this to help me see and ignore the fields that are normally null:

$ bw list items | /tmp/find_nulls.rb | cut -d '.' -f 2- | sort | uniq -c | sort -n

<!-- gh-comment-id:737021363 --> @nwallace commented on GitHub (Dec 2, 2020): I had the same issue happening on iOS. Turns out I had some bad data other clients handled fine, but the phone didn't. In my case, I had a Login URI whose URI was `null`. To find the borked data, I whipped up a Ruby script to help: ``` $ cat << EOF > /tmp/find_nulls.rb #! /usr/bin/env ruby require 'json' def find_nulls(item, path=[]) case item when Hash item.each do |k, v| find_nulls(v, path + [k]) end when Array item.each_with_index do |v, i| find_nulls(v, path + [i]) end when NilClass puts path.join(".") end end find_nulls(JSON.parse(STDIN.read)) EOF $ chmod +x /tmp/find_nulls.rb $ bw list items | /tmp/find_nulls.rb ``` You can scan the output manually to find fields that don't sound like they should be `null`, or use various other tools to help out. I did this to help me see and ignore the fields that are normally null: ``` $ bw list items | /tmp/find_nulls.rb | cut -d '.' -f 2- | sort | uniq -c | sort -n ```

kerem commented 2026-03-03 02:03:50 +03:00

Author

Owner

Copy link

@Starfiresg1 commented on GitHub (Dec 16, 2020):

I had the same issue on both my android devices.
The following procedure fixed it for me:
Updating my docker to the latest version (this alone didn't fix it)
Logging out of the vault on the Android App and logging back in (accessible through the 3 dots in the corner on the unlocking page)
After that I can unlock a locked vault without crash

Seems to me that the crash on unlocking is maybe created by the initial login with an older Bitwarden_rs version, because after the server update the issue still persisted until I logged in fresh.

<!-- gh-comment-id:746158508 --> @Starfiresg1 commented on GitHub (Dec 16, 2020): I had the same issue on both my android devices. The following procedure fixed it for me: Updating my docker to the latest version (this alone didn't fix it) Logging out of the vault on the Android App and logging back in (accessible through the 3 dots in the corner on the unlocking page) After that I can unlock a locked vault without crash Seems to me that the crash on unlocking is maybe created by the initial login with an older Bitwarden_rs version, because after the server update the issue still persisted until I logged in fresh.

kerem commented 2026-03-03 02:03:50 +03:00

Author

Owner

Copy link

@kenan435 commented on GitHub (Dec 18, 2020):

Seems to me that the crash on unlocking is maybe created by the initial login with an older Bitwarden_rs version, because after the server update the issue still persisted until I logged in fresh.

But that does not explain why logging in via biometrics works. I'd rather say that it happens while the master phrase is being validated.

<!-- gh-comment-id:747985570 --> @kenan435 commented on GitHub (Dec 18, 2020): > Seems to me that the crash on unlocking is maybe created by the initial login with an older Bitwarden_rs version, because after the server update the issue still persisted until I logged in fresh. But that does not explain why logging in via biometrics works. I'd rather say that it happens while the master phrase is being validated.

kerem commented 2026-03-03 02:03:50 +03:00

Author

Owner

Copy link

@BlackDex commented on GitHub (Dec 18, 2020):

It is because in the code of the client the master-password entered to unlock is verified at the server side.
But that wasn't available on the older versions of bitwarden_rs. Bio-Unlock bypasses this, because it doesn't have to verify the master-password. Maybe the client caches the 404 result, and just ignores a new request or something?

<!-- gh-comment-id:748055728 --> @BlackDex commented on GitHub (Dec 18, 2020): It is because in the code of the client the master-password entered to unlock is verified at the server side. But that wasn't available on the older versions of bitwarden_rs. Bio-Unlock bypasses this, because it doesn't have to verify the master-password. Maybe the client caches the 404 result, and just ignores a new request or something?

kerem commented 2026-03-03 02:03:50 +03:00

Author

Owner

Copy link

@daniellandau commented on GitHub (Jan 2, 2021):

For me it got fixed exactly as @Starfiresg1 described.

<!-- gh-comment-id:753511902 --> @daniellandau commented on GitHub (Jan 2, 2021): For me it got fixed exactly as @Starfiresg1 described.

kerem commented 2026-03-03 02:03:50 +03:00

Author

Owner

Copy link

@BlackDex commented on GitHub (Jan 29, 2021):

@nwallace, maybe a bit late. But a Uri as also Uris can definitely be null. What I'm curious about is, if for that same cipher if it at one place had uri or uris filled and not at the other. Or has uris filled but not uri. Do you still remember that?

<!-- gh-comment-id:770106483 --> @BlackDex commented on GitHub (Jan 29, 2021): @nwallace, maybe a bit late. But a Uri as also Uris can definitely be `null`. What I'm curious about is, if for that same cipher if it at one place had uri or uris filled and not at the other. Or has uris filled but not uri. Do you still remember that?

kerem commented 2026-03-03 02:03:50 +03:00

Author

Owner

Copy link

@BlackDex commented on GitHub (Jan 31, 2021):

Converting this issue to a discussion.

<!-- gh-comment-id:770412522 --> @BlackDex commented on GitHub (Jan 31, 2021): Converting this issue to a discussion.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

revert-7033-patch-1

cached-config-operations

test_dylint

1.35.8

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels   

SSO

  

Third party

  

better for forum

  

bug

  

bug

  

documentation

  

duplicate

  

enhancement

  

future Vault

  

future Vault

  

future Vault

  

good first issue

  

help wanted

  

low priority

  

notes

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

troubleshooting

  

wontfix

No labels

SSO

Third party

better for forum

bug

bug

documentation

duplicate

enhancement

future Vault

future Vault

future Vault

good first issue

help wanted

low priority

notes

pull-request

question

troubleshooting

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/vaultwarden#840

No description provided.