I’m using the latest version of Vaultwarden (1.32.5) and thought I’d give the new Android native app a try (Downloaded from here). Once I log into the app, it just crashes and refuses to launch. I’ve tried the release, beta, and dev apk’s, all with the same result. Once I went back to the current mobile version (Downloaded from here:), things worked properly again.
Is this incompatibility known, and is there anything that can be done on our end to make the new, native app work?
I’m using the beta Android app, which is the new version I believe, and it’s working fine with the latest VaultWarden docker instance. Try Google play rather than github.
Thanks for confirming that you’re able to use the new native app with Vaultwarden. I did join the beta and installed from the Play Store with the exact same results. Today, they merged the beta into the existing app and I tried again (v11.6), again with the crashes. Re-installed the old version (10.0) and things are fine, again.
My setup is as plain and ordinary Docker as they come (MySQL). Since nobody else has confirmed issues, I’m going to assume it’s something on my end and continue to try different things.
By the way, I did confirm that the Github betas and the Play Store betas were binary matches, so I’m certain that wasn’t the cause of my problems.
EDIT: My devices are both Google Pixel devices (7 and Tablet) running the latest Android 15. Same issue on both.
I use VaultWarden with the default database, which I think is SQLite. MySQL is an extra integration I think. I think if you want more help you’ll need to share screenshots, logs, configuration, etc.
Do your logs have anything relevant? Try the shell command “docker logs vaultwarden” assuming you’re on Linux.
I’m using a Pixel 8, VaultWarden is hosted on AWS EC2 with docker installed.
Thanks, again, for the response. And, you’re right, I’m also using SQLite. Mine is hosted in Docker on a Synology NAS and NOT exposed to the internet.
My initial inquiry wasn’t really aimed at troubleshooting the problem. I was merely trying to determine if it was a Vaultwarden issue or specific to my setup. Since it now appears specific to my setup, I’ll begin the troubleshooting once I return from my travels this coming weekend.
I’ll be certain and share my findings or post further questions with proper logs and more complete information.
That’s an odd problem. I’m not an expert but happy to continue to help if I can. I think logs are the next thing to look at.
I thought I’d share my final resolution to the problem I posted above. While I haven’t definitively identified whether this is a Vaultwarden problem or a Bitwarden (Android app) problem, I’m pretty certain it was caused by something in the Bitwarden Android app.
I had tried everything I could think of including completely recreating the Docker containers and re-importing my data… NOTHING resolved the issue with the (new) native Android client. Once login was completed in the app, the app just crashed. The Vaultwarden logs were of no help, either. They simply showed a successful login from the app and nothing about the subsequent crash - even when set to Debug logging.
As a last resort, I loaded up my vault export (json format) of 700+ passwords into a text editor and started scrolling through it, looking for any sort of anomaly. After a few minutes of this, I came across a VERY LARGE blob of data - thousands of lines of complete gibberish! Isolating it further, it was a ‘Password History’ entry belonging to a random login. After opening up Bitwarden in the desktop app to remove the password history for this entry, I found out there’s no way to remove password history for an item, so I used this work around to remove the bad entry.
After completing the removal of the contaminated item, everything works fine! So, while Vaultwarden had no problems with it, nor the Chrome Extension or the Bitwarden desktop client - the new native Android app couldn’t handle it.
My most likely guess as to how this happened is that I erroneously had this blob of data on my clipboard and accidentally saved it into a password field of an item. I probably immediately realized my mistake and simply over-wrote the blob with the proper data - sending the blob entry into the password history where it continued to live and cause problems.
Bitwarden should seriously consider adding an option to delete password history for an item. They also save the “hidden text” additional items into the password history which I would like to see eliminated as well. More than 50% of my vault export was Password History items belonging to these old “hidden text” entries.