github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-08-30 17:33:42 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #6751] [PM-34511] Session timeout ignored after app restart (locks immediately despite 4h setting) #88926

New Issue
Closed
opened 2026-05-27 01:29:41 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-27 01:29:41 -05:00
Owner
Copy Link
Copy Source

Originally created by @rrha on GitHub (Apr 1, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6751

Steps To Reproduce

  1. Open Bitwarden Android app
  2. Go to Settings → Security → Session timeout
  3. Set session timeout to "4 hours"
  4. Set "Session timeout action" to "Lock"
  5. Close the app
  6. Remove it from recent apps (force close / swipe away)
  7. Reopen the app

Expected Result

The vault should remain unlocked (or require unlock only after 4 hours of inactivity).

Actual Result

The app immediately requires unlock on reopen, behaving as if session timeout is set to "Immediately".

Screenshots or Videos

https://github.com/user-attachments/assets/9272c280-bbb7-472d-b72d-a52f1665eab0

Additional Context

  • This behavior persists even after changing the timeout from "Immediately" to "4 hours"
  • Seems like previous setting is still being enforced after app restart
  • Issue specifically happens when the app is removed from recent apps (fully closed)

Build Version

© Bitwarden Inc. 2015-2026 Version: 2026.3.0 (21345) 📱 Redmi M2103K19G 🤖 13@33 📦 prod 🧱 commit: bitwarden/android/release/2026.3-rc48@d8a9c596b27c9a68b63304d49784117bbebc6683 💻 build source: bitwarden/android/actions/runs/23011287575/attempts/1 🦀 SDK: 2.0.0-5425-a6f4a233 🌩 Server: 2026.3.2 @ US

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

  • Device: Xiaomi (Model: M2103K19G)
  • OS Version: Android 13 (TP1A.220624.014)
  • MIUI Version: MIUI Global 14.0.6 (14.0.6.0 TKSMIXM)
  • Android Security Patch: 2023-09-01

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 @rrha on GitHub (Apr 1, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6751 ### Steps To Reproduce 1. Open Bitwarden Android app 2. Go to Settings → Security → Session timeout 3. Set session timeout to "4 hours" 4. Set "Session timeout action" to "Lock" 5. Close the app 6. Remove it from recent apps (force close / swipe away) 7. Reopen the app ### Expected Result The vault should remain unlocked (or require unlock only after 4 hours of inactivity). ### Actual Result The app immediately requires unlock on reopen, behaving as if session timeout is set to "Immediately". ### Screenshots or Videos https://github.com/user-attachments/assets/9272c280-bbb7-472d-b72d-a52f1665eab0 ### Additional Context - This behavior persists even after changing the timeout from "Immediately" to "4 hours" - Seems like previous setting is still being enforced after app restart - Issue specifically happens when the app is removed from recent apps (fully closed) ### Build Version © Bitwarden Inc. 2015-2026 Version: 2026.3.0 (21345) 📱 Redmi M2103K19G 🤖 13@33 📦 prod 🧱 commit: bitwarden/android/release/2026.3-rc48@d8a9c596b27c9a68b63304d49784117bbebc6683 💻 build source: bitwarden/android/actions/runs/23011287575/attempts/1 🦀 SDK: 2.0.0-5425-a6f4a233 🌩 Server: 2026.3.2 @ US ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Device: Xiaomi (Model: M2103K19G) - OS Version: Android 13 (TP1A.220624.014) - MIUI Version: MIUI Global 14.0.6 (14.0.6.0 TKSMIXM) - Android Security Patch: 2023-09-01 ### 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 app:password-managerbug labels 2026-05-27 01:29:42 -05:00
GiteaMirror commented 2026-05-27 01:29:47 -05:00
Author
Owner
Copy Link
Copy Source

@bitwarden-bot commented on GitHub (Apr 1, 2026):

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

<!-- gh-comment-id:4167392297 --> @bitwarden-bot commented on GitHub (Apr 1, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-34511](https://bitwarden.atlassian.net/browse/PM-34511) [PM-34511]: https://bitwarden.atlassian.net/browse/PM-34511?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-05-27 01:29:53 -05:00
Author
Owner
Copy Link
Copy Source

@rrha commented on GitHub (Apr 1, 2026):

This appears to be related to #4477, but there haven't been any updates for a while, and the problem still persists .Apologies if this is a duplicate.

<!-- gh-comment-id:4167441166 --> @rrha commented on GitHub (Apr 1, 2026): This appears to be related to #4477, but there haven't been any updates for a while, and the problem still persists .Apologies if this is a duplicate.
GiteaMirror commented 2026-05-27 01:30:01 -05:00
Author
Owner
Copy Link
Copy Source

@rmcdowell-bitwarden commented on GitHub (Apr 1, 2026):

Hi there!

Thank you for taking the time submit this. This does appear to be a duplicate of the issue you mentioned, https://github.com/bitwarden/android/issues/4477

As we try to keep one open Issue for each reported bug, your issue will be closed.

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

Thanks!

<!-- gh-comment-id:4167603344 --> @rmcdowell-bitwarden commented on GitHub (Apr 1, 2026): Hi there! Thank you for taking the time submit this. This does appear to be a duplicate of the issue you mentioned, https://github.com/bitwarden/android/issues/4477 As we try to keep one open Issue for each reported bug, your issue will be closed. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these. Thanks!
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 labels app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#88926