[GH-ISSUE #6413] [BWA-222] When you try to log in to the Bitwarden mobile app (version 2025.12.1) against your self-hosted Vaultwarden/Bitwarden server and receive the error “MissingPropertyException #21698

Closed
opened 2026-04-16 22:16:47 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @diwanvasu on GitHub (Jan 26, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6413

Steps To Reproduce

Stacktrace:
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)
kv.w0.v0(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:24)
kv.k.q(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:93)
kv.k.n(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:3)
mv.i.a(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:7)
mv.g.I(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:76)
mv.g.i(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:53)
mv.g.h(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:97)
com.bitwarden.ui.platform.base.BaseViewModel.trySendAction(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:3)
fm.x.invoke(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:30)
com.bitwarden.ui.platform.components.util.ThrottledClickKt$throttledClick$1$1$1.invokeSuspend(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:41)
as.a.resumeWith(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:8)
kv.k0.run(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:115)
j4.t0.q0(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:24)
j4.s0.run(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:3)
android.os.Handler.handleCallback(Handler.java:1027)
android.os.Handler.dispatchMessage(Handler.java:108)
android.os.Looper.loopOnce(Looper.java:298)
android.os.Looper.loop(Looper.java:408)
android.app.ActivityThread.main(ActivityThread.java:9964)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:613)
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1074)

Version: 2025.12.1 (21060)
Device: 📱 OnePlus CPH2707 🤖 16@36 📦 prod
CI: 🧱 commit: bitwarden/android/release/2025.12-rc41@34888f8bc30d2ff1f352c6b1e964b6c2ad6d3e2f
💻 build source: bitwarden/android/actions/runs/20584595942/attempts/1

Expected Result

When you try to log in to the Bitwarden mobile app (version 2025.12.1) against your self-hosted Vaultwarden/Bitwarden server and receive the error “MissingPropertyException: Missing the required MasterPasswordUnlock data property,” it indicates that your mobile app is newer than your self-hosted server and expects authentication fields that your server does not provide. This happens due to an API/protocol mismatch, most commonly because Vaultwarden is outdated or incompatible with the latest official Bitwarden Android release. To resolve this, upgrade your self-hosted Vaultwarden server to the latest version, restart the container or Kubernetes pod, then fully log out and log back in on the mobile app. In nearly all self-hosted cases, updating Vaultwarden to the current vaultwarden/server:latest image fixes this login crash.

Actual Result

When you try to log in to the Bitwarden mobile app (version 2025.12.1) against your self-hosted Vaultwarden/Bitwarden server and receive the error “MissingPropertyException: Missing the required MasterPasswordUnlock data property,” it indicates that your mobile app is newer than your self-hosted server and expects authentication fields that your server does not provide. This happens due to an API/protocol mismatch, most commonly because Vaultwarden is outdated or incompatible with the latest official Bitwarden Android release. To resolve this, upgrade your self-hosted Vaultwarden server to the latest version, restart the container or Kubernetes pod, then fully log out and log back in on the mobile app. In nearly all self-hosted cases, updating Vaultwarden to the current vaultwarden/server:latest image fixes this login crash.

Screenshots or Videos

No response

Additional Context

No response

Build Version

1.32.3-alpine

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

No response

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 @diwanvasu on GitHub (Jan 26, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6413 ### Steps To Reproduce Stacktrace: 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) kv.w0.v0(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:24) kv.k.q(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:93) kv.k.n(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:3) mv.i.a(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:7) mv.g.I(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:76) mv.g.i(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:53) mv.g.h(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:97) com.bitwarden.ui.platform.base.BaseViewModel.trySendAction(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:3) fm.x.invoke(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:30) com.bitwarden.ui.platform.components.util.ThrottledClickKt$throttledClick$1$1$1.invokeSuspend(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:41) as.a.resumeWith(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:8) kv.k0.run(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:115) j4.t0.q0(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:24) j4.s0.run(r8-map-id-18d982514064553b029249dee47db6109adc97155b04b033017977809b50dc92:3) android.os.Handler.handleCallback(Handler.java:1027) android.os.Handler.dispatchMessage(Handler.java:108) android.os.Looper.loopOnce(Looper.java:298) android.os.Looper.loop(Looper.java:408) android.app.ActivityThread.main(ActivityThread.java:9964) java.lang.reflect.Method.invoke(Native Method) com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:613) com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1074) Version: 2025.12.1 (21060) Device: 📱 OnePlus CPH2707 🤖 16@36 📦 prod CI: 🧱 commit: bitwarden/android/release/2025.12-rc41@34888f8bc30d2ff1f352c6b1e964b6c2ad6d3e2f 💻 build source: bitwarden/android/actions/runs/20584595942/attempts/1 ### Expected Result When you try to log in to the Bitwarden mobile app (version 2025.12.1) against your self-hosted Vaultwarden/Bitwarden server and receive the error “MissingPropertyException: Missing the required MasterPasswordUnlock data property,” it indicates that your mobile app is newer than your self-hosted server and expects authentication fields that your server does not provide. This happens due to an API/protocol mismatch, most commonly because Vaultwarden is outdated or incompatible with the latest official Bitwarden Android release. To resolve this, upgrade your self-hosted Vaultwarden server to the latest version, restart the container or Kubernetes pod, then fully log out and log back in on the mobile app. In nearly all self-hosted cases, updating Vaultwarden to the current vaultwarden/server:latest image fixes this login crash. ### Actual Result When you try to log in to the Bitwarden mobile app (version 2025.12.1) against your self-hosted Vaultwarden/Bitwarden server and receive the error “MissingPropertyException: Missing the required MasterPasswordUnlock data property,” it indicates that your mobile app is newer than your self-hosted server and expects authentication fields that your server does not provide. This happens due to an API/protocol mismatch, most commonly because Vaultwarden is outdated or incompatible with the latest official Bitwarden Android release. To resolve this, upgrade your self-hosted Vaultwarden server to the latest version, restart the container or Kubernetes pod, then fully log out and log back in on the mobile app. In nearly all self-hosted cases, updating Vaultwarden to the current vaultwarden/server:latest image fixes this login crash. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 1.32.3-alpine ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details _No response_ ### 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.
GiteaMirror added the app:authenticatorbug labels 2026-04-16 22:16:47 -05:00
Author
Owner

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

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

<!-- gh-comment-id:3798565185 --> @bitwarden-bot commented on GitHub (Jan 26, 2026): Thank you for your report! We've added this to our internal board for review. ID: [BWA-222](https://bitwarden.atlassian.net/browse/BWA-222) [BWA-222]: https://bitwarden.atlassian.net/browse/BWA-222?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Author
Owner

@daniellbw commented on GitHub (Jan 26, 2026):

Hi there,

I attempted to reproduce your issue and was unable to do so.

Could you please try logging in and out of the application and see if that helps?

Could you please try restart the device (perform a full power cycle, shutting down and then restarting the device)?

If this doesn't work, please try reinstalling the Bitwarden app by following the below steps:

  • Uninstall the Bitwarden client
  • Restart the device (perform a full power cycle, shutting the device down completely and then restarting it)
  • Reinstall Bitwarden from the download link below

Bitwarden Downloads: https://bitwarden.com/download

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!

<!-- gh-comment-id:3798801764 --> @daniellbw commented on GitHub (Jan 26, 2026): Hi there, I attempted to reproduce your issue and was unable to do so. Could you please try logging in and out of the application and see if that helps? Could you please try restart the device (perform a full power cycle, shutting down and then restarting the device)? If this doesn't work, please try reinstalling the Bitwarden app by following the below steps: - Uninstall the Bitwarden client - Restart the device (perform a full power cycle, shutting the device down completely and then restarting it) - Reinstall Bitwarden from the download link below Bitwarden Downloads: https://bitwarden.com/download We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/). You can include a link to this issue in the message content. Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/). The issue here will be closed. Thanks!
Author
Owner

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

@daniellbw This essentially is/was a duplicate of https://github.com/bitwarden/android/issues/6363

<!-- gh-comment-id:3798867238 --> @pamperer562580892423 commented on GitHub (Jan 26, 2026): @daniellbw This essentially is/was a duplicate of https://github.com/bitwarden/android/issues/6363
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#21698