mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 08:39:46 +03:00
Latest Bitwarden Android app crashes when trying to add a new login entry #1738
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kiviktnm on GitHub (Oct 23, 2023).
Subject of the issue
Latest Bitwarden Android app crashes when trying to add a new login entry. The previous version of the app didn't do that. I also didn't encounter this issue when using the official Bitwarden servers (https://bitwarden.com). Sync works as expected.
I've tried clearing the Android app storage and cache as well as reinstalling the app.
Deployment environment
Install method: Vaultwarden enabled in NixOS options
Clients used: Android
Reverse proxy and version: Nginx 1.24.0
Other relevant details: Bitwarden Android app version 2023.9.2
More about Vaultwarden installation
I installed vaultwarden by enabling it in NixOS options basically the same way as it's done in the Deployment examples wiki page That runs the vaultwarden binary as a systemd service. It uses a SQLite database. I haven't tested this using other distros, so I hope it's not a NixOS specific bug.
If there are any details that are needed about the way NixOS does things I can look them up as I understand you don't want to spend time debugging NixOS.
The NixOS config used to run vaultwarden
I'm including this because it should tell what vaultwarden options I have set despite it being a nix file.
How NixOS creates the systemd service (=how vaultwarden is started)
This should tell how vaultwarden is started.
EnvironmentFile contains the environment variables that are used to configure vaultwarden.
Steps to reproduce
In the Android app press the '+'-button on the bottom right corner.
Type name, username and password.
Hit save on the top right.
App crashes.
Expected behaviour
The new login entry gets added to my vault.
Actual behaviour
Android app crashes.
Troubleshooting data
Vaultwarden logs
Not sure if these help.
Android app crash log
@stefan0xC commented on GitHub (Oct 23, 2023):
Given that the startup dialog doesn't say the version number, I think your Vaultwarden version is incompatible with the new server version requirement check that was implemented for the individual cipher encryption feature. You can confirm this by opening the
/api/configendpoint and look for theversionfield. If you didn't compile vaultwarden yourself, it might be an issue with the nixOS version (and possible other versions of vaultwarden, that don't have a version number).Weird, that they are not checking for a feature flag first in the bitwarden/mobile client (as it's done by the bitwarden/clients repository).
edit: should be fixed (for future releases) by #3990 as we now hard-code the required version number in this field.
@BlackDex commented on GitHub (Oct 23, 2023):
I do not have any issues, and I'm using v2023.9.2 on my android too.
And i'm using the the
testingtagged version just build today/yesterday.@BlackDex commented on GitHub (Oct 23, 2023):
I even had 2023.9.2 running before that, and i was able to add ciphers as far as i can tell.
But it might be only an update though, which will not change the way of the key per cipher.
@stefan0xC commented on GitHub (Oct 23, 2023):
@BlackDex your version of Vaultwarden probably had a
crate::VERSIONwhen it was build. (Might not have been the case for @kiviktnm / the build system of the affected third party package.)The dialog is missing the version output from
ecb31c85d6/src/main.rs (L222-L224)@BlackDex commented on GitHub (Oct 23, 2023):
ill test
@kiviktnm commented on GitHub (Oct 23, 2023):
This is it! The version field is
null. So are my options to wait for a new release that hard codes the version number or go looking for a NixOS solution to possibly compile vaultwarden myself and enable the version field?@BlackDex commented on GitHub (Oct 23, 2023):
Or, catch the
/api/configin your reverse proxy and serve it different content.@BlackDex commented on GitHub (Oct 23, 2023):
Going to close/move this, since it is already fixed.