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

vault gets locked every time app is swiped out of recents #2106

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

Originally created by @ristein on GitHub (Dec 15, 2024).

Steps To Reproduce

  1. Unlock vault
  2. Close app via recents swipe
  3. open app
  4. It's locked

Expected Result

should still be unlocked

Actual Result

need to type main password

Screenshots or Videos

No response

Additional Context

only happened after update to 2024.12.7
But older versions now show same behavior

Build Version

2024.12.7

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

Oneplus 7 pro, LineageOs 21, Android 14, no google, microG

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 @ristein on GitHub (Dec 15, 2024). ### Steps To Reproduce 1. Unlock vault 2. Close app via recents swipe 3. open app 4. It's locked ### Expected Result should still be unlocked ### Actual Result need to type main password ### Screenshots or Videos _No response_ ### Additional Context only happened after update to 2024.12.7 But older versions now show same behavior ### Build Version 2024.12.7 ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details Oneplus 7 pro, LineageOs 21, Android 14, no google, microG ### 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 2025-11-26 23:08:17 -06:00
GiteaMirror commented 2025-11-26 23:08:17 -06:00
Author
Owner
Copy Link

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

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

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

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

https://github.com/user-attachments/assets/5e0a393a-c8b3-4943-a8b0-ea3233e94da1

@ristein commented on GitHub (Dec 15, 2024): https://github.com/user-attachments/assets/5e0a393a-c8b3-4943-a8b0-ea3233e94da1
GiteaMirror commented 2025-11-26 23:08:18 -06:00
Author
Owner
Copy Link

@NovaSilentium commented on GitHub (Dec 16, 2024):

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

@NovaSilentium commented on GitHub (Dec 16, 2024): Hi there, I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
GiteaMirror commented 2025-11-26 23:08:18 -06:00
Author
Owner
Copy Link

@pasquale95 commented on GitHub (Jan 10, 2025):

@ristein I think you have Log out as Session timeout action in the Account Security section. Can you try also by setting the action to Lock?

@pasquale95 commented on GitHub (Jan 10, 2025): @ristein I think you have `Log out` as **Session timeout action** in the **Account Security** section. Can you try also by setting the action to `Lock`?
GiteaMirror commented 2025-11-26 23:08:18 -06:00
Author
Owner
Copy Link

@ristein commented on GitHub (Jan 10, 2025):

it was always set to lock.
I updated yesterday to 2025.1.0 from F-Droid but no change

@ristein commented on GitHub (Jan 10, 2025): it was always set to lock. I updated yesterday to 2025.1.0 from F-Droid but no change
GiteaMirror commented 2025-11-26 23:08:18 -06:00
Author
Owner
Copy Link

@bfhrud commented on GitHub (Jan 11, 2025):

Hello, same problem.
Version: 2025.1.0 (google play)
Settings: Auto-LOCK after 10 minutes (custom) Also using PIN. Battery management for Bitwarden in android set to unlimited.

After swiping Bitwarden out from recently opened apps - Bitwarden SOMETIMES lock totally - then I have to type in master password instead of a pin. But not everytime. Is it desired behavior? I thought that it should lock only after the time I set. And then it should ask for PIN anyways. Thank you for answer.

EDIT: Is it possible that is has connection with setting up the accessibility? Because when I turn on accessibility in bitwarden settings and in android (for Bitwarden's quick-action tile), then problem disappears. Bitwarden doesn't lock prematurely, and also after locking, it demands only PIN. (I think this is expected behaviour?) In addition, the accessibility setting does not seem turned on, even when it is. After forcing bitwarden to close (in android settings), then accessibility setting in Bitwarden turns off and Bitwarden once again locks prematurely and demands master password after swiping out of the recents.

@bfhrud commented on GitHub (Jan 11, 2025): Hello, same problem. Version: 2025.1.0 (google play) Settings: Auto-LOCK after 10 minutes (custom) Also using PIN. Battery management for Bitwarden in android set to unlimited. After swiping Bitwarden out from recently opened apps - Bitwarden SOMETIMES lock totally - then I have to type in master password instead of a pin. But not everytime. Is it desired behavior? I thought that it should lock only after the time I set. And then it should ask for PIN anyways. Thank you for answer. EDIT: Is it possible that is has connection with setting up the accessibility? Because when I turn on accessibility in bitwarden settings and in android (for Bitwarden's quick-action tile), then problem disappears. Bitwarden doesn't lock prematurely, and also after locking, it demands only PIN. (I think this is expected behaviour?) In addition, the accessibility setting does not seem turned on, even when it is. After forcing bitwarden to close (in android settings), then accessibility setting in Bitwarden turns off and Bitwarden once again locks prematurely and demands master password after swiping out of the recents.
GiteaMirror commented 2025-11-26 23:08:18 -06:00
Author
Owner
Copy Link

@ristein commented on GitHub (Jan 13, 2025):

thank you for the workaround.
Enabling accessibility also works for me

@ristein commented on GitHub (Jan 13, 2025): thank you for the workaround. Enabling accessibility also works for me
GiteaMirror commented 2025-11-26 23:08:19 -06:00
Author
Owner
Copy Link

@pasquale95 commented on GitHub (Jan 22, 2025):

I don't want to enable the "Accessibility" functionality to fix this problem.
Bitwarden was working fine before the latest update even without the "Accessibility" function turned on.

@pasquale95 commented on GitHub (Jan 22, 2025): I don't want to enable the "Accessibility" functionality to fix this problem. Bitwarden was working fine before the latest update even without the "Accessibility" function turned on.
GiteaMirror commented 2025-11-26 23:08:19 -06:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Nov 18, 2025):

⚠️ Stale Issue Notice

This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (December 02, 2025) if no further activity occurs.

If this issue is still relevant and you would like to keep it open, please:

  • Comment on this issue to show continued interest
  • Provide any additional information or updates
  • Confirm that the issue still exists in the latest version

Thank you for your contribution to this project! 🙏

@closebot-bw commented on GitHub (Nov 18, 2025): ⚠️ **Stale Issue Notice** This issue has been automatically marked as stale due to inactivity. It will be closed in **2 weeks** (December 02, 2025) if no further activity occurs. If this issue is still relevant and you would like to keep it open, please: - Comment on this issue to show continued interest - Provide any additional information or updates - Confirm that the issue still exists in the latest version Thank you for your contribution to this project! 🙏
GiteaMirror commented 2025-11-26 23:08:19 -06:00
Author
Owner
Copy Link

@VVispy commented on GitHub (Nov 18, 2025):

Im still experiencing this issue

@VVispy commented on GitHub (Nov 18, 2025): Im still experiencing this issue
GiteaMirror commented 2025-11-26 23:08:19 -06:00
Author
Owner
Copy Link

@ristein commented on GitHub (Nov 18, 2025):

I have not seen this problem in quite a while 🤷

@ristein commented on GitHub (Nov 18, 2025): I have not seen this problem in quite a while 🤷
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 app:password-manager 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#2106
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?