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

Android app ignores locking timeout instuctions #1527

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

Originally created by @gitrascal on GitHub (Nov 10, 2022).

Steps To Reproduce

Settings > Security > Vault timeout. Choose time to lock the app (for example 4 hours).
Close the app, lock/unlock the device and try logging in on random website, bitwarden will be locked and will be needed to unlock again.

Expected Result

When I set the timeout on 4 hours, I want it to be unlocked the entire time instead of being locked after my phone gets locked/unlocked.

Actual Result

Bitwarden gets locked in a few minutes whenever I lock my device instead of my timeout instruction of 4 hours

Screenshots or Videos

No response

Additional Context

No response

Operating System

Android

Operating System Version

One UI 4.1 October Security Patch

Device

Samsung Galaxy A52s

Build Version

Version: 2022.10.0 (5247)

Beta

  • Using a pre-release version of the application.
Originally created by @gitrascal on GitHub (Nov 10, 2022). ### Steps To Reproduce Settings > Security > Vault timeout. Choose time to lock the app (for example 4 hours). Close the app, lock/unlock the device and try logging in on random website, bitwarden will be locked and will be needed to unlock again. ### Expected Result When I set the timeout on 4 hours, I want it to be unlocked the entire time instead of being locked after my phone gets locked/unlocked. ### Actual Result Bitwarden gets locked in a few minutes whenever I lock my device instead of my timeout instruction of 4 hours ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Operating System Android ### Operating System Version One UI 4.1 October Security Patch ### Device Samsung Galaxy A52s ### Build Version Version: 2022.10.0 (5247) ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:51:34 -06:00
GiteaMirror commented 2025-11-26 22:51:34 -06:00
Author
Owner
Copy Link

@RuthlessRuler commented on GitHub (Nov 20, 2022):

Can reproduce the same.

@RuthlessRuler commented on GitHub (Nov 20, 2022): Can reproduce the same.
GiteaMirror commented 2025-11-26 22:51:34 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Dec 8, 2022):

Same issue here it prompts for my PIN every time I close and reopen the app. Version 2022.11.0 on Android.

@vinnyperella commented on GitHub (Dec 8, 2022): Same issue here it prompts for my PIN every time I close and reopen the app. Version 2022.11.0 on Android.
GiteaMirror commented 2025-11-26 22:51:35 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Jan 11, 2023):

I just updated to the latest version 2023.01.0 and this is still an issue it asks for my master password anytime I close the app regardless of lock settings. This is very very annoying.

@vinnyperella commented on GitHub (Jan 11, 2023): I just updated to the latest version 2023.01.0 and this is still an issue it asks for my master password anytime I close the app regardless of lock settings. This is very very annoying.
GiteaMirror commented 2025-11-26 22:51:35 -06:00
Author
Owner
Copy Link

@shrimprugbysnowowl commented on GitHub (Feb 14, 2023):

I'm running v2023.1.0 and have it set to unlock with a PIN, but it still asks for my Master Password each time.

@shrimprugbysnowowl commented on GitHub (Feb 14, 2023): > I'm running v2023.1.0 and have it set to unlock with a PIN, but it still asks for my Master Password each time.
GiteaMirror commented 2025-11-26 22:51:35 -06:00
Author
Owner
Copy Link

@nkm8 commented on GitHub (Feb 22, 2023):

Issue still persists in v2023.2.0 - and I have tried all of the available vault timeout options. Even custom with a really long duration results in the vault locking very quickly.

This is frustrating because autofill on Android works poorly for me when Bitwarden is locked.

@nkm8 commented on GitHub (Feb 22, 2023): Issue still persists in v2023.2.0 - and I have tried all of the available vault timeout options. Even custom with a really long duration results in the vault locking very quickly. This is frustrating because autofill on Android works poorly for me when Bitwarden is locked.
GiteaMirror commented 2025-11-26 22:51:35 -06:00
Author
Owner
Copy Link

@nkm8 commented on GitHub (Feb 22, 2023):

Related issues:
https://github.com/bitwarden/mobile/issues/1718
https://github.com/bitwarden/mobile/issues/858
https://github.com/bitwarden/mobile/issues/1557
https://github.com/bitwarden/mobile/issues/1363

I can confirm the issue still exists with battery usage set to unrestricted.

@nkm8 commented on GitHub (Feb 22, 2023): Related issues: https://github.com/bitwarden/mobile/issues/1718 https://github.com/bitwarden/mobile/issues/858 https://github.com/bitwarden/mobile/issues/1557 https://github.com/bitwarden/mobile/issues/1363 I can confirm the issue still exists with battery usage set to unrestricted.
GiteaMirror commented 2025-11-26 22:51:36 -06:00
Author
Owner
Copy Link

@nkm8 commented on GitHub (Feb 22, 2023):

I played around with this issue a bit more. I was really perplexed because the timeout options recently worked fine for me.

I found that the vault timeout setting only works when the Bitwarden accessibility service is enabled. You can test this behavior:

  1. Disable accessibility service
  2. Set vault timeout to never
  3. Force close Bitwarden
  4. Reopen Bitwarden
  5. See prompt to unlock vault

If you repeat these steps with the accessibility service enabled, you will no longer be promoted to unlock the vault (correct behavior).

I need the accessibility service to be disabled due to a bug in Gmail where the toast prompts never disappear while any accessibility service is enabled.

@nkm8 commented on GitHub (Feb 22, 2023): I played around with this issue a bit more. I was really perplexed because the timeout options recently worked fine for me. I found that the vault timeout setting only works when the Bitwarden accessibility service is enabled. You can test this behavior: 1. Disable accessibility service 2. Set vault timeout to never 3. Force close Bitwarden 4. Reopen Bitwarden 5. See prompt to unlock vault If you repeat these steps with the accessibility service enabled, you will no longer be promoted to unlock the vault (correct behavior). I need the accessibility service to be disabled due to a bug in Gmail where the toast prompts never disappear while any accessibility service is enabled.
GiteaMirror commented 2025-11-26 22:51:36 -06:00
Author
Owner
Copy Link

@2fst4u commented on GitHub (Feb 23, 2023):

Enabling accessibility for bitwarden did not resolve the issue for me.

@2fst4u commented on GitHub (Feb 23, 2023): Enabling accessibility for bitwarden did not resolve the issue for me.
GiteaMirror commented 2025-11-26 22:51:36 -06:00
Author
Owner
Copy Link

@shrimprugbysnowowl commented on GitHub (Feb 26, 2023):

I played around with this issue a bit more. I was really perplexed because the timeout options recently worked fine for me.

I found that the vault timeout setting only works when the Bitwarden accessibility service is enabled. You can test this behavior:

  1. Disable accessibility service
  2. Set vault timeout to never
  3. Force close Bitwarden
  4. Reopen Bitwarden
  5. See prompt to unlock vault

If you repeat these steps with the accessibility service enabled, you will no longer be promoted to unlock the vault (correct behavior).

I need the accessibility service to be disabled due to a bug in Gmail where the toast prompts never disappear while any accessibility service is enabled.

By George, I think you've done it! This resolves my issue, but it appears that others experiencing the same or a similar issue are still having the problem, so I can leave this open.

@shrimprugbysnowowl commented on GitHub (Feb 26, 2023): > I played around with this issue a bit more. I was really perplexed because the timeout options recently worked fine for me. > > I found that the vault timeout setting only works when the Bitwarden accessibility service is enabled. You can test this behavior: > > 1. Disable accessibility service > 2. Set vault timeout to never > 3. Force close Bitwarden > 4. Reopen Bitwarden > 5. See prompt to unlock vault > > If you repeat these steps with the accessibility service enabled, you will no longer be promoted to unlock the vault (correct behavior). > > I need the accessibility service to be disabled due to a bug in Gmail where the toast prompts never disappear while any accessibility service is enabled. By George, I think you've done it! This resolves my issue, but it appears that others experiencing the same or a similar issue are still having the problem, so I can leave this open.
GiteaMirror commented 2025-11-26 22:51:36 -06:00
Author
Owner
Copy Link

@shrimprugbysnowowl commented on GitHub (Feb 26, 2023):

Enabling accessibility for bitwarden did not resolve the issue for me.

Enable accessibility then disable and reenable your PIN. Accepting the prompt that is titled "Unlock with PIN code" worked for me.

@shrimprugbysnowowl commented on GitHub (Feb 26, 2023): > Enabling accessibility for bitwarden did not resolve the issue for me. Enable accessibility then disable and reenable your PIN. Accepting the prompt that is titled "Unlock with PIN code" worked for me.
GiteaMirror commented 2025-11-26 22:51:36 -06:00
Author
Owner
Copy Link

@2fst4u commented on GitHub (Feb 27, 2023):

Enabling accessibility for bitwarden did not resolve the issue for me.

Enable accessibility then disable and reenable your PIN. Accepting the prompt that is titled "Unlock with PIN code" worked for me.

Still no change for me.

@2fst4u commented on GitHub (Feb 27, 2023): > > Enabling accessibility for bitwarden did not resolve the issue for me. > > Enable accessibility then disable and reenable your PIN. Accepting the prompt that is titled "Unlock with PIN code" worked for me. Still no change for me.
GiteaMirror commented 2025-11-26 22:51:37 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 5, 2023):

I can reproduce this bug if app is removed from recents or force closed. Not sure if that is expected?

@ghost commented on GitHub (Mar 5, 2023): I can reproduce this bug if app is removed from recents or force closed. Not sure if that is expected?
GiteaMirror commented 2025-11-26 22:51:37 -06:00
Author
Owner
Copy Link

@shrimprugbysnowowl commented on GitHub (Mar 8, 2023):

Enabling accessibility for bitwarden did not resolve the issue for me.

Enable accessibility then disable and reenable your PIN. Accepting the prompt that is titled "Unlock with PIN code" worked for me.

Update: This appears to only work until the device is restarted or the android profile is changed, then Bitwarden prompts for the master password again. It seems to obey the lock time setting and locks with the PIN if configured. This still happens even if Bitwarden is swiped out of the recents for me, but prompts for the master password again if it's forced to close from android settings. Is this repeatable for anyone?

@shrimprugbysnowowl commented on GitHub (Mar 8, 2023): > > Enabling accessibility for bitwarden did not resolve the issue for me. > > Enable accessibility then disable and reenable your PIN. Accepting the prompt that is titled "Unlock with PIN code" worked for me. Update: This appears to only work until the device is restarted or the android profile is changed, then Bitwarden prompts for the master password again. It seems to obey the lock time setting and locks with the PIN if configured. This still happens even if Bitwarden is swiped out of the recents for me, but prompts for the master password again if it's forced to close from android settings. Is this repeatable for anyone?
GiteaMirror commented 2025-11-26 22:51:37 -06:00
Author
Owner
Copy Link

@cvlc12 commented on GitHub (Mar 16, 2023):

Also an issue for me.

By the way, enabling accessibility services shouldn't be considered a solution.

Thanks !

@cvlc12 commented on GitHub (Mar 16, 2023): Also an issue for me. By the way, enabling accessibility services shouldn't be considered a solution. Thanks !
GiteaMirror commented 2025-11-26 22:51:37 -06:00
Author
Owner
Copy Link

@colleenmason commented on GitHub (Apr 2, 2023):

Also having this issue in ios. specifically if I set vault timeout to "never", leave settings and return (not even leaving the app just go to main screen and back into settings) the timeout has reverted to "15 minutes"

@colleenmason commented on GitHub (Apr 2, 2023): Also having this issue in ios. specifically if I set vault timeout to "never", leave settings and return (not even leaving the app just go to main screen and back into settings) the timeout has reverted to "15 minutes"
GiteaMirror commented 2025-11-26 22:51:38 -06:00
Author
Owner
Copy Link

@rogerfar commented on GitHub (Apr 2, 2023):

Tried it in android again and the setting is just ignored.

@rogerfar commented on GitHub (Apr 2, 2023): Tried it in android again and the setting is just ignored.
GiteaMirror commented 2025-11-26 22:51:38 -06:00
Author
Owner
Copy Link

@colleenmason commented on GitHub (Apr 2, 2023):

I cried to the bitwarden twitter and they suggested uninstall/reinstall the app. That actually worked for me! Again I'm on ios so I don't know if it'll help on Android but I figured I'd report my success fingers crossed for y'all

@colleenmason commented on GitHub (Apr 2, 2023): I cried to the bitwarden twitter and they suggested uninstall/reinstall the app. That actually worked for me! Again I'm on ios so I don't know if it'll help on Android but I figured I'd report my success fingers crossed for y'all
GiteaMirror commented 2025-11-26 22:51:38 -06:00
Author
Owner
Copy Link

@cvlc12 commented on GitHub (Apr 10, 2023):

This is still an issue for me on Android. Reinstalling did not solve anything.

@cvlc12 commented on GitHub (Apr 10, 2023): This is still an issue for me on Android. Reinstalling did not solve anything.
GiteaMirror commented 2025-11-26 22:51:39 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (May 16, 2023):

This is still an issue for me as well has not been fixed in all of the releases since the issue was reported.

@vinnyperella commented on GitHub (May 16, 2023): This is still an issue for me as well has not been fixed in all of the releases since the issue was reported.
GiteaMirror commented 2025-11-26 22:51:39 -06:00
Author
Owner
Copy Link

@RuthlessRuler commented on GitHub (May 16, 2023):

Same. It hasn't been resolved for me too. Either we need to create a new issue or @VakHub pleaee re-open this issue

@RuthlessRuler commented on GitHub (May 16, 2023): Same. It hasn't been resolved for me too. Either we need to create a new issue or @VakHub pleaee re-open this issue
GiteaMirror commented 2025-11-26 22:51:39 -06:00
Author
Owner
Copy Link

@dany2007 commented on GitHub (Jun 23, 2023):

The issue is also present on my phone (Poco F4) with all the battery saving options disabled. This has been a problem since i started using bitwarden a few months ago.

@dany2007 commented on GitHub (Jun 23, 2023): The issue is also present on my phone (Poco F4) with all the battery saving options disabled. This has been a problem since i started using bitwarden a few months ago.
GiteaMirror commented 2025-11-26 22:51:39 -06:00
Author
Owner
Copy Link

@SlimGary commented on GitHub (Jul 1, 2023):

Same here, Xiaomi 13 and pixel 7, all battery saving options disabled

@SlimGary commented on GitHub (Jul 1, 2023): Same here, Xiaomi 13 and pixel 7, all battery saving options disabled
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#1527
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?