[GH-ISSUE #4464] 2024.11.7 gets locked on every close #77194

Closed
opened 2026-05-19 13:41:14 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @ristein on GitHub (Dec 13, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/4464

Steps To Reproduce

  1. Unlock
  2. Close (swipe out of recents)
  3. Open
  4. Unlock again

Expected Result

should not need main password until set timeout

Actual Result

need to unlock with main password

Screenshots or Videos

No response

Additional Context

No response

Build Version

2024.11.7 (F-Droid)

What server are you connecting to?

Self-host

Self-host Server Version

Vaultwarden Web Version 2024.6.2

Environment Details

Oneplus 7 pro, Lineageos 21, Android 14, no google

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 @ristein on GitHub (Dec 13, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/4464 ### Steps To Reproduce 1. Unlock 2. Close (swipe out of recents) 3. Open 4. Unlock again ### Expected Result should not need main password until set timeout ### Actual Result need to unlock with main password ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2024.11.7 (F-Droid) ### What server are you connecting to? Self-host ### Self-host Server Version Vaultwarden Web Version 2024.6.2 ### Environment Details Oneplus 7 pro, Lineageos 21, Android 14, no google ### 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 bug label 2026-05-19 13:41:14 -05:00
Author
Owner

@bitwarden-bot commented on GitHub (Dec 13, 2024):

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

<!-- gh-comment-id:2541144403 --> @bitwarden-bot commented on GitHub (Dec 13, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-15991
Author
Owner

@NovaSilentium commented on GitHub (Dec 13, 2024):

Hi there,

It is important to note that vaultwarden is not associated with Bitwarden.

Vaultwarden is a re-writing of the Bitwarden server code in Rust, that is not contributed to or 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.

Bitwarden also offers a self-hosted option, which many of our customers run in an air-gapped environment. You can find information on this here:

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

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

This issue will be closed. Thank you for understanding.

<!-- gh-comment-id:2541597359 --> @NovaSilentium commented on GitHub (Dec 13, 2024): Hi there, It is important to note that vaultwarden is not associated with Bitwarden. Vaultwarden is a re-writing of the Bitwarden server code in Rust, that is not contributed to or 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. Bitwarden also offers a self-hosted option, which many of our customers run in an air-gapped environment. You can find information on this here: https://bitwarden.com/help/install-on-premise-linux/ https://bitwarden.com/help/install-and-deploy-offline/ This issue will be closed. Thank you for understanding.
Author
Owner

@ristein commented on GitHub (Dec 13, 2024):

Do you think the different locking behavior after an update of the vault on my phone has to do with the server?

<!-- gh-comment-id:2541630736 --> @ristein commented on GitHub (Dec 13, 2024): Do you think the different locking behavior after an update of the vault on my phone has to do with the server?
Author
Owner

@ristein commented on GitHub (Dec 13, 2024):

I tried few older releases and they all have the same behavior.
I also tried with official server which shows the same problem.

<!-- gh-comment-id:2542438028 --> @ristein commented on GitHub (Dec 13, 2024): I tried few older releases and they all have the same behavior. I also tried with official server which shows the same problem.
Author
Owner

@juliokele commented on GitHub (Feb 11, 2025):

I had the same problem. After uninstalling and reinstalling the application, it seems to work as expected.

<!-- gh-comment-id:2651862726 --> @juliokele commented on GitHub (Feb 11, 2025): I had the same problem. After uninstalling and reinstalling the application, it seems to work as expected.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#77194