github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-08-13 22:08:44 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #6363] [PM-30831] MissingPropertyException: Missing the required MasterPasswordUnlock with 2025.12.1 #15065

New Issue
Closed
opened 2026-04-15 01:23:21 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-15 01:23:21 -05:00
Owner
Copy Link
Copy Source

Originally created by @Lion62 on GitHub (Jan 15, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6363

Steps To Reproduce

GitHub Bug Report: Android App 2025.12.1 - MissingPropertyException

Title: [Android] MissingPropertyException: Missing the required MasterPasswordUnlock

Description: Since the update to version 2025.12.1, the Android application fails to sync and crashes/errors with a MissingPropertyException regarding MasterPasswordUnlock. This issue was not present in version 2025.12.0.

Steps to Reproduce:

Use Bitwarden Android app version 2025.12.1.

Connect to a self-hosted Vaultwarden server (v1.34.3) Home assistant version

Attempt to perform a manual sync or log in.

The application fails with the stacktrace provided below.

Expected Behavior: The application should sync successfully with the self-hosted server as it did in version 2025.12.0.

Actual Behavior: The sync fails and the app throws a com.bitwarden.core.data.repository.error.MissingPropertyException.

Environment:

Device: POCO 24117RK2CG

Android Version: 16

Bitwarden App Version: 2025.12.1 (21060)

Server: Vaultwarden 1.34.3 (self-hosted via Home Assistant)

Stacktrace:
Java

com.bitwarden.core.data.repository.error.MissingPropertyException: Missing the required MasterPasswordUnlock data property
zk.s.S(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:164)
a2.f1.invokeSuspend(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:476)
as.a.resumeWith(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:8)
kv.k0.run(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:115)
[...]

Expected Result

Actual Result

Screenshots or Videos

No response

Additional Context

No response

Build Version

2025.12.1

What server are you connecting to?

Self-host

Self-host Server Version

1.34.3

Environment Details

Poco F7 pro

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @Lion62 on GitHub (Jan 15, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6363 ### Steps To Reproduce GitHub Bug Report: Android App 2025.12.1 - MissingPropertyException Title: [Android] MissingPropertyException: Missing the required MasterPasswordUnlock Description: Since the update to version 2025.12.1, the Android application fails to sync and crashes/errors with a MissingPropertyException regarding MasterPasswordUnlock. This issue was not present in version 2025.12.0. Steps to Reproduce: Use Bitwarden Android app version 2025.12.1. Connect to a self-hosted Vaultwarden server (v1.34.3) Home assistant version Attempt to perform a manual sync or log in. The application fails with the stacktrace provided below. Expected Behavior: The application should sync successfully with the self-hosted server as it did in version 2025.12.0. Actual Behavior: The sync fails and the app throws a com.bitwarden.core.data.repository.error.MissingPropertyException. Environment: Device: POCO 24117RK2CG Android Version: 16 Bitwarden App Version: 2025.12.1 (21060) Server: Vaultwarden 1.34.3 (self-hosted via Home Assistant) Stacktrace: Java com.bitwarden.core.data.repository.error.MissingPropertyException: Missing the required MasterPasswordUnlock data property zk.s.S(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:164) a2.f1.invokeSuspend(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:476) as.a.resumeWith(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:8) kv.k0.run(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:115) [...] ### Expected Result - ### Actual Result - ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2025.12.1 ### What server are you connecting to? Self-host ### Self-host Server Version 1.34.3 ### Environment Details Poco F7 pro ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the app:password-managerbug labels 2026-04-15 01:23:21 -05:00
GiteaMirror commented 2026-04-15 01:23:22 -05:00
Author
Owner
Copy Link
Copy Source

@bitwarden-bot commented on GitHub (Jan 15, 2026):

Thank you for your report! We've added this to our internal board for review.
ID: PM-30831

<!-- gh-comment-id:3752352290 --> @bitwarden-bot commented on GitHub (Jan 15, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-30831](https://bitwarden.atlassian.net/browse/PM-30831) [PM-30831]: https://bitwarden.atlassian.net/browse/PM-30831?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-15 01:23:23 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Jan 15, 2026):

Only another user here...

And there is a merged PR that seems to have a connection: https://github.com/bitwarden/android/pull/6176

But anyway...

Server: Vaultwarden 1.34.3 (self-hosted via Home Assistant)

... you probably should contact Vaultwarden. - And in general: When you use Vaultwarden instead of Bitwarden, you should have a look at this info from Vaultwarden about reporting potential bugs: https://github.com/dani-garcia/vaultwarden/wiki/Bitwarden-clients-troubleshooting

<!-- gh-comment-id:3752360947 --> @pamperer562580892423 commented on GitHub (Jan 15, 2026): Only another user here... And there is a merged PR that seems to have a connection: https://github.com/bitwarden/android/pull/6176 But anyway... > Server: Vaultwarden 1.34.3 (self-hosted via Home Assistant) ... you probably should contact Vaultwarden. - And in general: When you use Vaultwarden instead of Bitwarden, you should have a look at this info from Vaultwarden about reporting potential bugs: https://github.com/dani-garcia/vaultwarden/wiki/Bitwarden-clients-troubleshooting
GiteaMirror commented 2026-04-15 01:23:23 -05:00
Author
Owner
Copy Link
Copy Source

@rmcdowell-bitwarden commented on GitHub (Jan 15, 2026):

It is important to note that Vaultwarden is not associated with Bitwarden. Vaultwarden is a re-writing of the Bitwarden server code in Rust (n.b. Vaultwarden is NOT a fork of Bitwarden), that is not contributed to nor supported by the Bitwarden team or organization. The security audits granted to Bitwarden do not apply to Vaultwarden, and the Bitwarden support team is not able to respond to questions regarding Vaultwarden. Support options for Vaultwarden are found here:

https://github.com/dani-garcia/vaultwarden?tab=readme-ov-file#get-in-touch

Bitwarden also offers a self-hosted option, with multiple deployment options, including for air-gapped deployments. You can find information on Bitwarden’s deployment options here:

https://bitwarden.com/help/install-on-premise-linux/

https://bitwarden.com/help/install-and-deploy-offline/

If you would like to know more about a Bitwarden self-hosted setup, I will happily put you in touch with our Sales Team, who will be able to provide you with a trial license. You can also initiate this yourself here:

https://bitwarden.com/help/enterprise-free-trial/

This issue will now be closed.

<!-- gh-comment-id:3752610961 --> @rmcdowell-bitwarden commented on GitHub (Jan 15, 2026): It is important to note that Vaultwarden is not associated with Bitwarden. Vaultwarden is a re-writing of the Bitwarden server code in Rust (n.b. Vaultwarden is NOT a fork of Bitwarden), that is not contributed to nor supported by the Bitwarden team or organization. The security audits granted to Bitwarden do not apply to Vaultwarden, and the Bitwarden support team is not able to respond to questions regarding Vaultwarden. Support options for Vaultwarden are found here: https://github.com/dani-garcia/vaultwarden?tab=readme-ov-file#get-in-touch Bitwarden also offers a self-hosted option, with multiple deployment options, including for air-gapped deployments. You can find information on Bitwarden’s deployment options here: https://bitwarden.com/help/install-on-premise-linux/ https://bitwarden.com/help/install-and-deploy-offline/ If you would like to know more about a Bitwarden self-hosted setup, I will happily put you in touch with our Sales Team, who will be able to provide you with a trial license. You can also initiate this yourself here: https://bitwarden.com/help/enterprise-free-trial/ This issue will now be closed.
GiteaMirror commented 2026-04-15 01:23:23 -05:00
Author
Owner
Copy Link
Copy Source

@Bapf commented on GitHub (Jan 18, 2026):

If other Vaultwarden-Users end up here:

Updating your Vaultwarden server and afterwards logging out and in again on the Android client fixes the issue.

<!-- gh-comment-id:3765203648 --> @Bapf commented on GitHub (Jan 18, 2026): If other Vaultwarden-Users end up here: Updating your Vaultwarden server _and_ afterwards logging out and in again on the Android client fixes the issue.
GiteaMirror commented 2026-04-15 01:23:24 -05:00
Author
Owner
Copy Link
Copy Source

@erdnuesse commented on GitHub (Jan 21, 2026):

If other Vaultwarden-Users end up here:

Updating your Vaultwarden server and afterwards logging out and in again on the Android client fixes the issue.

Also: quickly downgrading the app to 2025.12.0 (if you're on the go and can't homelab in a pinch) may be a temporary fix until you can do a proper (and hopefully backed up and tested) server upgrade.

<!-- gh-comment-id:3778944771 --> @erdnuesse commented on GitHub (Jan 21, 2026): > If other Vaultwarden-Users end up here: > > Updating your Vaultwarden server _and_ afterwards logging out and in again on the Android client fixes the issue. Also: quickly downgrading the app to 2025.12.0 (if you're on the go and can't homelab in a pinch) may be a temporary fix until you can do a proper (and hopefully backed up and tested) server upgrade.
GiteaMirror commented 2026-04-15 01:23:24 -05:00
Author
Owner
Copy Link
Copy Source

@sa1g commented on GitHub (Jan 24, 2026):

If other Vaultwarden-Users end up here:

Updating your Vaultwarden server and afterwards logging out and in again on the Android client fixes the issue.

If this doesn't work try updating vaultwarden, then uninstall -> install the bitwarden App

<!-- gh-comment-id:3794689685 --> @sa1g commented on GitHub (Jan 24, 2026): > If other Vaultwarden-Users end up here: > > Updating your Vaultwarden server _and_ afterwards logging out and in again on the Android client fixes the issue. If this doesn't work try updating vaultwarden, then uninstall -> install the bitwarden App
GiteaMirror commented 2026-04-15 01:23:25 -05:00
Author
Owner
Copy Link
Copy Source

@Mic92 commented on GitHub (Jan 25, 2026):

For me uninstalling and installing from the Playstore didn't solve the issue, but than somehow installing bitwarden from their f-droid repository did (exact same version). Very strange, because I would assume this is an issue with API responses from vaultwarden that should trigger the bug in both versions.

<!-- gh-comment-id:3796278573 --> @Mic92 commented on GitHub (Jan 25, 2026): For me uninstalling and installing from the Playstore didn't solve the issue, but than somehow installing bitwarden from their f-droid repository did (exact same version). Very strange, because I would assume this is an issue with API responses from vaultwarden that should trigger the bug in both versions.
GiteaMirror commented 2026-04-15 01:23:26 -05:00
Author
Owner
Copy Link
Copy Source

@SergeantConfused commented on GitHub (Jan 25, 2026):

Hello everyone,

I wanted to mention that this behavior may occur in certain cases whilst using the Bitwarden cloud. If you encounter this, please log out and log in anew, instead of unlocking the logged-in session, and that should assist. If that does not assist, please proceed and uninstall Bitwarden off your mobile device, turn your device off (long press) and back on, install Bitwarden anew from the operating system's official application store (Apple App Store/Google Play Store), and test that once more.

In case this behavior persists, please feel free to get in touch with the Bitwarden Customer Success team.

All the best,

<!-- gh-comment-id:3796599800 --> @SergeantConfused commented on GitHub (Jan 25, 2026): Hello everyone, I wanted to mention that this behavior may occur in certain cases whilst using the Bitwarden cloud. If you encounter this, please [log out and log in anew](https://bitwarden.com/help/understand-log-in-vs-unlock/), instead of unlocking the logged-in session, and that should assist. If that does not assist, please proceed and uninstall Bitwarden off your mobile device, turn your device off (long press) and back on, install Bitwarden anew from the operating system's official application store (Apple App Store/Google Play Store), and test that once more. In case this behavior persists, please feel free to [get in touch](https://bitwarden.com/help/) with the Bitwarden Customer Success team. All the best,
GiteaMirror commented 2026-04-15 01:23:26 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Jan 25, 2026):

that this behavior may occur in certain cases whilst using the Bitwarden cloud.

@SergeantConfused I would guess - and wanted to add - that those who self-host Bitwarden probably also could encounter it (?!) and also have to make sure, that they have the latest server version installed. Right?!

<!-- gh-comment-id:3796617545 --> @pamperer562580892423 commented on GitHub (Jan 25, 2026): > that this behavior may occur in certain cases whilst using the Bitwarden cloud. @SergeantConfused I would guess - and wanted to add - that those who self-host Bitwarden probably also could encounter it (?!) and also have to make sure, that they have the latest server version installed. Right?!
GiteaMirror commented 2026-04-15 01:23:27 -05:00
Author
Owner
Copy Link
Copy Source

@QbikEdge commented on GitHub (Mar 29, 2026):

i am also posting this here maybe it will help someone:

For me it is solved by updating my server from Vaultwarden Web 2025.1.1 to Vaultwarden Web 2026.1.1

important
i tried to update it by pulling the latest-alpine images for docker it did not work
but by changing the image just to latest it work.

<!-- gh-comment-id:4150935407 --> @QbikEdge commented on GitHub (Mar 29, 2026): i am also posting this here maybe it will help someone: For me it is solved by updating my server from `Vaultwarden Web 2025.1.1` to `Vaultwarden Web 2026.1.1` > important i tried to update it by pulling the `latest-alpine` images for docker it did not work but by changing the image just to `latest` it work.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No labels app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#15065