github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 19:39:41 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #4436] Timeout is not honored when screen is locked #27985

New Issue
Closed
opened 2026-04-18 11:44:10 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-18 11:44:10 -05:00
Owner
Copy Link

Originally created by @Sedeniono on GitHub (Dec 9, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/4436

Steps To Reproduce

  1. Open the Bitwarden app.
  2. Set the "Session timeout" to 1 minute (for ease of reproduction) and the session timeout action to "Lock".
  3. Lock the screen of the phone (while the bitwarden app is still in the foreground) by pressing the device's power button to turn off the screen.
  4. Wait more than 1 minute while the phone is locked.
  5. Press the power button and unlock the phone via the phone's password/PIN/etc.
  6. The bitwarden app is still in the foreground. The problem is: The vault is still unlocked, although the timeout period should have run out.

Expected Result

The bitwarden vault should be locked after the configured timeout passed, even if the phone itself got locked during the timeout period.

Actual Result

The bitwarden vault does not get locked.

Screenshots or Videos

No response

Additional Context

  • If you do not lock the phone during the timeout period, but instead use some other apps, and then you go back to bitwarden, the vault is locked.
  • You can also set a timeout of e.g. 5 or 15 minutes. The same thing happens: If the screen gets locked during this timeout period and you wait longer than the timeout, the vault remains unlocked.
  • You can also "minimize" the bitwarden app before locking the phone. With "minimize" I mean to go to some other app or the home screen. The result is the same.
  • If you first unlock the vault, then "minimize" the bitwarden app, then lock the phone for a few seconds, then unlock the phone, then wait for more than 1 minute without opening the bitwarden app, and then open the bitwarden app, the vault is locked.

=> To me it looks like the "timeout timer" in the bitwarden app gets paused as soon as the phone gets locked. And it gets resumed while the phone is unlocked.

Build Version

2024.11.7 (19528) from Google Play

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

Google Pixel 4a, Android 13, Build number TQ3A-230805.001.S1

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 @Sedeniono on GitHub (Dec 9, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/4436 ### Steps To Reproduce 1. Open the Bitwarden app. 2. Set the "Session timeout" to 1 minute (for ease of reproduction) and the session timeout action to "Lock". 3. Lock the screen of the phone (while the bitwarden app is still in the foreground) by pressing the device's power button to turn off the screen. 4. Wait more than 1 minute while the phone is locked. 5. Press the power button and unlock the phone via the phone's password/PIN/etc. 6. The bitwarden app is still in the foreground. The problem is: The vault is still unlocked, although the timeout period should have run out. ### Expected Result The bitwarden vault should be **locked** after the configured timeout passed, even if the phone itself got locked during the timeout period. ### Actual Result The bitwarden vault does **not** get locked. ### Screenshots or Videos _No response_ ### Additional Context * If you do **not** lock the phone during the timeout period, but instead use some other apps, and then you go back to bitwarden, the vault **is** locked. * You can also set a timeout of e.g. 5 or 15 minutes. The same thing happens: If the screen gets locked during this timeout period and you wait longer than the timeout, the vault remains unlocked. * You can also "minimize" the bitwarden app before locking the phone. With "minimize" I mean to go to some other app or the home screen. The result is the same. * If you first unlock the vault, then "minimize" the bitwarden app, then lock the phone for a few seconds, then unlock the phone, then wait for more than 1 minute without opening the bitwarden app, and then open the bitwarden app, the vault is locked. => To me it looks like the "timeout timer" in the bitwarden app gets paused as soon as the phone gets locked. And it gets resumed while the phone is unlocked. ### Build Version 2024.11.7 (19528) from Google Play ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details Google Pixel 4a, Android 13, Build number TQ3A-230805.001.S1 ### 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-04-18 11:44:10 -05:00
GiteaMirror commented 2026-04-18 11:44:11 -05:00
Author
Owner
Copy Link

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

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

<!-- gh-comment-id:2527214229 --> @bitwarden-bot commented on GitHub (Dec 9, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-15804
GiteaMirror commented 2026-04-18 11:44:12 -05:00
Author
Owner
Copy Link

@Krychaz commented on GitHub (Dec 12, 2024):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

<!-- gh-comment-id:2538446216 --> @Krychaz commented on GitHub (Dec 12, 2024): Hi there, Thank you for your report! I was able to reproduce this issue, and I have flagged this to our engineering team. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again!
GiteaMirror commented 2026-04-18 11:44:12 -05:00
Author
Owner
Copy Link

@differsthecat commented on GitHub (Jan 27, 2025):

Fixed in #4610

<!-- gh-comment-id:2616816487 --> @differsthecat commented on GitHub (Jan 27, 2025): Fixed in #4610
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 Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#27985
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?