github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-13 13:44:36 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Vault Timeout is not honored on Android - it locks immediately and forces me to authenticate everytime I need to autofill a password. #1347

New Issue
Closed
opened 2025-11-26 22:45:41 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-26 22:45:41 -06:00
Owner
Copy Link

Originally created by @jmannrider on GitHub (Sep 22, 2021).

Steps To Reproduce

  1. Go to Bitwarden->Settings->Vault Timeout
  2. Select any timeout option other than immediately. I'll select 'Never'
  3. Go to any app that allows you to auto-fill a password
  4. Unlock vault and fill password in.
  5. Go to any other app and autofill password.
  6. Notice that the vault is already locked and must authenticate to unlock it again.

Expected Result

I would expect to not have to authenticate again if 'Never' is selected as the timeout option.

Actual Result

Vault locks immediately despite the option you've selected.

Screenshots or Videos

No response

Additional Context

I have troubleshooted this by making sure that the phone's battery settings is not killing the app. Bitwarden is set to never be put to sleep or optimized at all. I have already ran out of options.
I have also contacted support but they weren't able to offer me a solution.

Operating System

Android

Operating System Version

9

Web Browser

N/A- Only app.

Browser Version

N/A

Build Version

2.12.0(3742)

Originally created by @jmannrider on GitHub (Sep 22, 2021). ### Steps To Reproduce 1. Go to Bitwarden->Settings->Vault Timeout 2. Select any timeout option other than immediately. I'll select 'Never' 3. Go to any app that allows you to auto-fill a password 4. Unlock vault and fill password in. 5. Go to any other app and autofill password. 6. Notice that the vault is already locked and must authenticate to unlock it again. ### Expected Result I would expect to not have to authenticate again if 'Never' is selected as the timeout option. ### Actual Result Vault locks immediately despite the option you've selected. ### Screenshots or Videos _No response_ ### Additional Context I have troubleshooted this by making sure that the phone's battery settings is not killing the app. Bitwarden is set to never be put to sleep or optimized at all. I have already ran out of options. I have also contacted support but they weren't able to offer me a solution. ### Operating System Android ### Operating System Version 9 ### Web Browser N/A- Only app. ### Browser Version N/A ### Build Version 2.12.0(3742)
GiteaMirror commented 2025-11-26 22:45:41 -06:00
Author
Owner
Copy Link

@gschintgen commented on GitHub (Apr 5, 2022):

I can confirm (on Android) that I'm constantly asked to unlock my vault even though I tried setting the timeout to 4 hours.
Version: 2.16.2 (4334)

@gschintgen commented on GitHub (Apr 5, 2022): I can confirm (on Android) that I'm constantly asked to unlock my vault even though I tried setting the timeout to 4 hours. Version: 2.16.2 (4334)
GiteaMirror commented 2025-11-26 22:45:42 -06:00
Author
Owner
Copy Link

@gschintgen commented on GitHub (Apr 5, 2022):

Update: it does work for me after all if I disable battery savings:
Settings/Apps/Bitwarden/Battery/Unrestricted
This is on a Samsung Galaxy S10e (Android 12)

Sorry for the noise...

@gschintgen commented on GitHub (Apr 5, 2022): Update: it *does* work for me after all if I disable battery savings: Settings/Apps/Bitwarden/Battery/Unrestricted This is on a Samsung Galaxy S10e (Android 12) Sorry for the noise...
GiteaMirror commented 2025-11-26 22:45:42 -06:00
Author
Owner
Copy Link

@ps2goat commented on GitHub (Sep 28, 2023):

This just started happening to me today. I've had this set up on my phone since Jan 2022 and have used it every day since. I'm on a Samsung A32(?). Version 2023.9.1

Every time I navigate away or need to authority, I have to sign in again.

@ps2goat commented on GitHub (Sep 28, 2023): This just started happening to me today. I've had this set up on my phone since Jan 2022 and have used it every day since. I'm on a Samsung A32(?). Version 2023.9.1 Every time I navigate away or need to authority, I have to sign in again.
GiteaMirror commented 2025-11-26 22:45:42 -06:00
Author
Owner
Copy Link

@ImSkully commented on GitHub (Oct 28, 2023):

Also experiencing this issue since some time in August, there is a forum topic (and #2182) on this issue with many other users reporting the same.

Rolling back to version 2023.8.0 seems to fix this so a change released after this has re-introduced this problem again, at least for me anyway.

@ImSkully commented on GitHub (Oct 28, 2023): Also experiencing this issue since some time in August, there is a [forum topic](https://community.bitwarden.com/t/vault-locks-automatically-when-timeout-is-disabled-in-android-app/58506/11) *(and #2182)* on this issue with many other users reporting the same. Rolling back to version [2023.8.0](https://www.apkmirror.com/apk/bitwarden-inc/bitwarden-password-manager/bitwarden-password-manager-2023-8-0-release/bitwarden-password-manager-2023-8-0-2-android-apk-download/) seems to fix this so a change released after this has re-introduced this problem again, at least for me anyway.
GiteaMirror commented 2025-11-26 22:45:43 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Nov 1, 2023):

I just updated to 2023.10.0 which states in the notes "Bug fix for timeout settings not being respected" but I'm still seeing the issue. If I set my vault timeout to 5 minutes, swipe Bitwarden out of my recent apps, then open Bitwarden again it prompts me for my PIN regardless of the timeout setting. If I keep Bitwarden in my recent apps after 5 minutes it prompts me for my PIN which is the correct behavior. Not sure if this is intended I can't remember which version this started occurring on but I know it wasn't always the case.

This also screws up the "enter master password when app is restarted" feature I used to have enabled. If you enable that and swipe Bitwarden out of your recent apps it will prompt you for your master password. It used to only prompt for your master password if the app was updated or the device was restarted. This is super annoying as this is a very good feature for security that I simply cannot use anymore.

@vinnyperella commented on GitHub (Nov 1, 2023): I just updated to 2023.10.0 which states in the notes "Bug fix for timeout settings not being respected" but I'm still seeing the issue. If I set my vault timeout to 5 minutes, swipe Bitwarden out of my recent apps, then open Bitwarden again it prompts me for my PIN regardless of the timeout setting. If I keep Bitwarden in my recent apps after 5 minutes it prompts me for my PIN which is the correct behavior. Not sure if this is intended I can't remember which version this started occurring on but I know it wasn't always the case. This also screws up the "enter master password when app is restarted" feature I used to have enabled. If you enable that and swipe Bitwarden out of your recent apps it will prompt you for your master password. It used to only prompt for your master password if the app was updated or the device was restarted. This is super annoying as this is a very good feature for security that I simply cannot use anymore.
GiteaMirror commented 2025-11-26 22:45:43 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Nov 29, 2023):

Any update on this issue?

@vinnyperella commented on GitHub (Nov 29, 2023): Any update on this issue?
GiteaMirror commented 2025-11-26 22:45:44 -06:00
Author
Owner
Copy Link

@meiersa78 commented on GitHub (Jun 5, 2024):

Just started using Bitwarden and this issue is driving me mad. Apparently, it's been years and nothing has been done... When will there be a fix for Android? Reddit is full of posts about this very problem. I can set any time, custom time, never, but BW just locks me out. I disabled any battery optimization for the app. I even locked the app so it never gets closed by Android, but still, BW just locks the vault all the time, no matter if set to 5 minutes, 4 hours or never. This is so frustrating! What's the point of that setting if it doesn't work at all?! Ah, and I tried biometric unlock and the pin method. I also cleared data and cache, I uninstalled and reinstalled the app countless times. It doesn't work!

@meiersa78 commented on GitHub (Jun 5, 2024): Just started using Bitwarden and this issue is driving me mad. Apparently, it's been years and nothing has been done... When will there be a fix for Android? Reddit is full of posts about this very problem. I can set any time, custom time, never, but BW just locks me out. I disabled any battery optimization for the app. I even locked the app so it never gets closed by Android, but still, BW just locks the vault all the time, no matter if set to 5 minutes, 4 hours or never. This is so frustrating! What's the point of that setting if it doesn't work at all?! Ah, and I tried biometric unlock and the pin method. I also cleared data and cache, I uninstalled and reinstalled the app countless times. It doesn't work!
GiteaMirror commented 2025-11-26 22:45:44 -06:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/1557

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/1557
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
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#1347
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?