What app is this about, and its version: Vaultwarden v1.35.2-ynh1 What YunoHost version are you running: 12.1.39 (stable) What type of hardware are you using: Old laptop or computer
Describe your issue
Android upgraded my Bitwarden client and suddenly I can’t access Vaultwarden on YNH. The android Bitwarden app can access pukka Bitwarden accounts on their eu and us servers but not my self-hosted version. Wierdly, accessing the YNH Vaultwarden app from a browser works fine.
If I log in to Vaultwarden from my android app it logs in fine but then says I have to verify the master password that I just used to log in. Each time I enter the master password it fails to unlock the account. I know the master password is fine as it’s accepted from via a browser login.
This is similar to an error seen before but not resolved. Is it just me or have others got the same problem?
Share relevant logs or error messages
Stacktrace:
com.bitwarden.core.data.repository.error.MissingPropertyException: Missing the required MasterPasswordUnlock data property
This is a known bug introduced by the Bitwarden Android app version 2025.12.1. Many users have reported this exact issue since mid-January 2026.
Your Vaultwarden version (1.35.2-ynh1) is already the correct one, it includes the server-side fix for this compatibility issue.
Problem:
The Android app update changed how authentication works, and even though your server is compatible, your local app session may be corrupted or outdated.
Solution:
In the Bitwarden Android app, go to Settings and log out completely (not just lock the vault)
Log back in with your server URL and credentials
If that doesn’t work:
Uninstall the Bitwarden app completely
Reinstall it from the Play Store
Log in again
This has been confirmed to work by multiple users facing the same issue :
The key takeaway from the Vaultwarden maintainer (BlackDex): the fix requires both Vaultwarden 1.35.2+ on the server side (which you have) AND clearing the corrupted session on the client side by logging out/in or reinstalling.
Yes, after upgrading Bitwarden on my phone, I encountered precisely this. the Android app absolutely bungled how it handles the master password unlock attribute — nothing wrong with your Vaultwarden server. To be honest, the only thing that worked for me was to log out completely, delete the app’s cache, and then log back in using the complete server URL. merely locking/unlocking doesn’t cut it anymore. The 2025.12.1 update completely corrupts the session data, therefore the only certain way to repair it if that doesn’t work is to remove and reinstall. Vaultwarden is operating normally; this is only a Bitwarden client problem on Android.