the vault isn't locked when the screen gets locked #2132

Closed
opened 2025-11-26 23:08:54 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @grrosminet on GitHub (Jan 16, 2025).

Steps To Reproduce

  1. unlock your vault
  2. get out of the app
  3. turn off the screen
  4. turn on the screen
  5. unlock your device
  6. go back to the app

Expected Result

the vault should be locked, like it used to be with the old app

Actual Result

the vault is NOT locked

Screenshots or Videos

No response

Additional Context

No response

Build Version

2025.1.0 (19622) (FDroid-prod repo)

What server are you connecting to?

Self-host

Self-host Server Version

No response

Environment Details

Samsung Z-Flip 5
Android 14

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 @grrosminet on GitHub (Jan 16, 2025). ### Steps To Reproduce 1. unlock your vault 2. get out of the app 3. turn off the screen 4. turn on the screen 5. unlock your device 6. go back to the app ### Expected Result the vault should be locked, like it used to be with the old app ### Actual Result the vault is NOT locked ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2025.1.0 (19622) (FDroid-prod repo) ### What server are you connecting to? Self-host ### Self-host Server Version _No response_ ### Environment Details Samsung Z-Flip 5 Android 14 ### 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 2025-11-26 23:08:54 -06:00
Author
Owner

@bitwarden-bot commented on GitHub (Jan 16, 2025):

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

@bitwarden-bot commented on GitHub (Jan 16, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-17159
Author
Owner

@micahblut commented on GitHub (Jan 16, 2025):

Can you please describe what settings you are using for your session timeout and session timeout action? These can be found in Settings > Account Security

@micahblut commented on GitHub (Jan 16, 2025): Can you please describe what settings you are using for your session timeout and session timeout action? These can be found in Settings > Account Security
Author
Owner

@grrosminet commented on GitHub (Jan 16, 2025):

I use :
Biometric unlock
No pin
Session timeout : 15 minutes
After timeout : lock

16 janv. 2025 13:27:58 medelblut @.***>:

Can you please describe what settings you are using for your session timeout and session timeout action? These can be found in Settings > Account Security


Reply to this email directly, view it on GitHub[https://github.com/bitwarden/android/issues/4573#issuecomment-2595453626], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAXQUKY62NIDSRW6LZ5M4MD2K6QUTAVCNFSM6AAAAABVI6SUICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJVGQ2TGNRSGY].
You are receiving this because you authored the thread.
[Image de pistage][https://github.com/notifications/beacon/AAXQUK6A344NYZLHVEDZSZD2K6QUTA5CNFSM6AAAAABVI6SUICWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTU2WN5LU.gif]

@grrosminet commented on GitHub (Jan 16, 2025): I use : Biometric unlock No pin Session timeout : 15 minutes After timeout : lock 16 janv. 2025 13:27:58 medelblut ***@***.***>: > > Can you please describe what settings you are using for your session timeout and session timeout action? These can be found in Settings > Account Security > > — > Reply to this email directly, view it on GitHub[https://github.com/bitwarden/android/issues/4573#issuecomment-2595453626], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAXQUKY62NIDSRW6LZ5M4MD2K6QUTAVCNFSM6AAAAABVI6SUICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJVGQ2TGNRSGY]. > You are receiving this because you authored the thread. > [Image de pistage][https://github.com/notifications/beacon/AAXQUK6A344NYZLHVEDZSZD2K6QUTA5CNFSM6AAAAABVI6SUICWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTU2WN5LU.gif] >
Author
Owner

@micahblut commented on GitHub (Jan 16, 2025):

In this case, you should expect your vault will remain unlocked until 15 minutes have elapsed. We do not currently have a "on device lock" option for timeout. If that is something you're interested in, I recommend submitting a feature request in our community forum: https://community.bitwarden.com/t/about-the-feature-requests-category/12

@micahblut commented on GitHub (Jan 16, 2025): In this case, you should expect your vault will remain unlocked until 15 minutes have elapsed. We do not currently have a "on device lock" option for timeout. If that is something you're interested in, I recommend submitting a feature request in our community forum: https://community.bitwarden.com/t/about-the-feature-requests-category/12
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#2132