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.