[GH-ISSUE #6613] [PM-33156] unlock with master password fails #66294

Closed
opened 2026-05-14 08:14:20 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @wscherphof on GitHub (Mar 4, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6613

Steps To Reproduce

  1. Log in self hosted
  2. Enter master password to unlock
  3. Stacktrace:
    com.bitwarden.core.data.repository.error.MissingPropertyException: Missing the required MasterPasswordUnlock data property
    yk.s.V(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:164)
    a2.g1.invokeSuspend(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:1098)
    bs.a.resumeWith(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:8)
    lv.j0.run(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:115)
    lv.v0.v0(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:24)
    lv.k.q(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:93)
    lv.k.n(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:3)
    nv.i.a(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:7)
    nv.g.I(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:76)
    nv.g.h(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:53)
    nv.g.i(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:97)
    com.bitwarden.ui.platform.base.BaseViewModel.trySendAction(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:3)
    em.x.invoke(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:30)
    com.bitwarden.ui.platform.components.util.ThrottledClickKt$throttledClick$1$1$1.invokeSuspend(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:41)
    bs.a.resumeWith(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:8)
    lv.j0.run(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:115)
    h4.u0.q0(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:24)
    h4.t0.run(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:3)
    android.os.Handler.handleCallback(Handler.java:959)
    android.os.Handler.dispatchMessage(Handler.java:100)
    android.os.Looper.loopOnce(Looper.java:232)
    android.os.Looper.loop(Looper.java:317)
    android.app.ActivityThread.main(ActivityThread.java:8751)
    java.lang.reflect.Method.invoke(Native Method)
    com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580)
    com.android.internal.os.ZygoteInit.main(ZygoteInit.java:892)

Version: 2026.2.0 (21203)
Device: 📱 Fairphone FP4 🤖 15@35 📦 prod
CI: 🧱 commit: bitwarden/android/release/2026.2-rc46@cbe13d2015f97955de1e0f11a229330ddd4654c0
💻 build source: bitwarden/android/actions/runs/21762978463/attempts/1

Expected Result

App unlocked by entering correct master password

Actual Result

Error message with provided stack trace

Screenshots or Videos

No response

Additional Context

No response

Build Version

2026.2.0

What server are you connecting to?

Self-host

Self-host Server Version

unknown

Environment Details

Fairphone 4, up to date

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 @wscherphof on GitHub (Mar 4, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6613 ### Steps To Reproduce 1. Log in self hosted 2. Enter master password to unlock 3. Stacktrace: com.bitwarden.core.data.repository.error.MissingPropertyException: Missing the required MasterPasswordUnlock data property yk.s.V(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:164) a2.g1.invokeSuspend(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:1098) bs.a.resumeWith(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:8) lv.j0.run(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:115) lv.v0.v0(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:24) lv.k.q(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:93) lv.k.n(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:3) nv.i.a(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:7) nv.g.I(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:76) nv.g.h(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:53) nv.g.i(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:97) com.bitwarden.ui.platform.base.BaseViewModel.trySendAction(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:3) em.x.invoke(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:30) com.bitwarden.ui.platform.components.util.ThrottledClickKt$throttledClick$1$1$1.invokeSuspend(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:41) bs.a.resumeWith(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:8) lv.j0.run(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:115) h4.u0.q0(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:24) h4.t0.run(r8-map-id-5283ced94ef91aff8251a71242ee24b09bb97bec3f9db0e69844d0d0fe10118e:3) android.os.Handler.handleCallback(Handler.java:959) android.os.Handler.dispatchMessage(Handler.java:100) android.os.Looper.loopOnce(Looper.java:232) android.os.Looper.loop(Looper.java:317) android.app.ActivityThread.main(ActivityThread.java:8751) java.lang.reflect.Method.invoke(Native Method) com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580) com.android.internal.os.ZygoteInit.main(ZygoteInit.java:892) Version: 2026.2.0 (21203) Device: 📱 Fairphone FP4 🤖 15@35 📦 prod CI: 🧱 commit: bitwarden/android/release/2026.2-rc46@cbe13d2015f97955de1e0f11a229330ddd4654c0 💻 build source: bitwarden/android/actions/runs/21762978463/attempts/1 ### Expected Result App unlocked by entering correct master password ### Actual Result Error message with provided stack trace ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2026.2.0 ### What server are you connecting to? Self-host ### Self-host Server Version unknown ### Environment Details Fairphone 4, up to date ### 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 bugapp:password-manager labels 2026-05-14 08:14:20 -05:00
Author
Owner

@bitwarden-bot commented on GitHub (Mar 4, 2026):

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

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

@pamperer562580892423 commented on GitHub (Mar 4, 2026):

Duplicate of https://github.com/bitwarden/android/issues/6363

<!-- gh-comment-id:4000378301 --> @pamperer562580892423 commented on GitHub (Mar 4, 2026): Duplicate of https://github.com/bitwarden/android/issues/6363
Author
Owner

@sshadminBW commented on GitHub (Mar 4, 2026):

Hello @wscherphof

Thanks for the report!

  1. If you're using the Bitwarden cloud, please log out and try to log in anew. More about this here (https://bitwarden.com/help/understand-log-in-vs-unlock/).
  2. If step 1 does not assist, please uninstall the Bitwarden mobile client off your device, turn the device completely off (long press) and back on, install Bitwarden anew from the Google Play Store/Apple App Store and try to log in then.
  3. If using Vaultwarden, updating your Vaultwarden server and afterwards logging out and in again on the Android client fixes the issue.

Thanks
Bitwarden Support.

<!-- gh-comment-id:4000385592 --> @sshadminBW commented on GitHub (Mar 4, 2026): Hello @wscherphof Thanks for the report! 1. If you're using the Bitwarden cloud, please log out and try to log in anew. More about this here (https://bitwarden.com/help/understand-log-in-vs-unlock/). 2. If step 1 does not assist, please uninstall the Bitwarden mobile client off your device, turn the device completely off (long press) and back on, install Bitwarden anew from the Google Play Store/Apple App Store and try to log in then. 3. If using Vaultwarden, updating your Vaultwarden server and afterwards logging out and in again on the Android client fixes the issue. Thanks Bitwarden Support.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#66294