github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-22 12:32:53 -05:00
Code Issues 144 Packages Projects Releases 93 Wiki Activity

Session timeout not working #2105

New Issue
Closed
opened 2025-11-26 23:08:16 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-26 23:08:16 -06:00
Owner
Copy Link

Originally created by @m0yP on GitHub (Dec 14, 2024).

Steps To Reproduce

Biometrics enabled.
Session timeout set to "On app restart".
Session timeout action set to "Lock".

Expected Result

Vault should stay unlocked until app restarts. It was working fine on previous builds.

Actual Result

Vault locks and app asks for biometrics, even if no password was selected or app was opened from drawer.

Screenshots or Videos

No response

Additional Context

This issue started happening when updated app to v2024.11.7(19528).

Build Version

2024.11.7 (19528) F-Droid from Bitwarden repo

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Samsung Galaxy S24 Ultra
Android 14, OneUI 6.1

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 @m0yP on GitHub (Dec 14, 2024). ### Steps To Reproduce Biometrics enabled. Session timeout set to "On app restart". Session timeout action set to "Lock". ### Expected Result Vault should stay unlocked until app restarts. It was working fine on previous builds. ### Actual Result Vault locks and app asks for biometrics, even if no password was selected or app was opened from drawer. ### Screenshots or Videos _No response_ ### Additional Context This issue started happening when updated app to v2024.11.7(19528). ### Build Version 2024.11.7 (19528) F-Droid from Bitwarden repo ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Samsung Galaxy S24 Ultra Android 14, OneUI 6.1 ### 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:16 -06:00
GiteaMirror commented 2025-11-26 23:08:17 -06:00
Author
Owner
Copy Link

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

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

@bitwarden-bot commented on GitHub (Dec 14, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-16063
GiteaMirror commented 2025-11-26 23:08:17 -06:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Dec 15, 2024):

Hello @m0yP,

Thank you for reporting this. I tested this on Android 14 by setting the Vault Timeout/Action to (On app restart/Lock) whilst (Unlock with biometrics) is activated, and I left the phone; the Bitwarden Android client was unlocked when I launched it after ~12 hours. I'd recommend checking if another application or a setting in the operating system is killing the Bitwarden client whilst it's in the background.

If this behaviour persists, please feel free to create a Support ticket so we'd have a look at this together, and please also include a link to this GitHub report in the body of your ticket.

Alternatively, you can seek assistance from other Bitwarden users in our Community Forums, if you wish.

We use GitHub to track potential bugs and other development related matters; This GitHub report will be closed at this point.

Thank you again,

@SergeantConfused commented on GitHub (Dec 15, 2024): Hello @m0yP, Thank you for reporting this. I tested this on Android 14 by setting the Vault Timeout/Action to (On app restart/Lock) whilst (Unlock with biometrics) is activated, and I left the phone; the Bitwarden Android client was unlocked when I launched it after ~12 hours. I'd recommend checking if another application or a setting in the operating system is killing the Bitwarden client whilst it's [in the background](https://dontkillmyapp.com/). If this behaviour persists, please feel free to create a [Support ticket](https://bitwarden.com/help/) so we'd have a look at this together, and please also include a link to this GitHub report in the body of your ticket. Alternatively, you can seek assistance from other Bitwarden users in our [Community Forums](https://community.bitwarden.com/c/support/), if you wish. We use GitHub to track potential bugs and other development related matters; This GitHub report will be closed at this point. Thank you again,
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#2105
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?