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

[PM-26115] Exiting the app doesn't lock the vault #2357

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

Originally created by @jasttw on GitHub (Sep 23, 2025).

Steps To Reproduce

  1. Install a recent bitwarden version (it wasn't like this before a recent update)
  2. Exit the app from the menu
  3. Confirm exiting the app
  4. Open the app again before the timeout period

Expected Result

I would expect the vault to lock after explicitly exiting the app. Similar behaviour to windows app and probably every other app that ends the process when exiting

Actual Result

The app opens with the vault unlocked

Screenshots or Videos

No response

Additional Context

Currently, it gives a false impression of security when exiting and confirming exiting when all it does is just send the app to the background. It was locking with the old app, then stopped working when the app was rebuilt, then worked again, then stopped working in a recent update.

Build Version

2025.9.0 (20692)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Android on Samsung Galaxy

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 @jasttw on GitHub (Sep 23, 2025). ### Steps To Reproduce 1. Install a recent bitwarden version (it wasn't like this before a recent update) 2. Exit the app from the menu 3. Confirm exiting the app 4. Open the app again before the timeout period ### Expected Result I would expect the vault to lock after explicitly exiting the app. Similar behaviour to windows app and probably every other app that ends the process when exiting ### Actual Result The app opens with the vault unlocked ### Screenshots or Videos _No response_ ### Additional Context Currently, it gives a false impression of security when exiting and confirming exiting when all it does is just send the app to the background. It was locking with the old app, then stopped working when the app was rebuilt, then worked again, then stopped working in a recent update. ### Build Version 2025.9.0 (20692) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Android on Samsung Galaxy ### 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:16:40 -06:00
GiteaMirror commented 2025-11-26 23:16:41 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Sep 23, 2025):

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

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

@cbw23 commented on GitHub (Sep 29, 2025):

Hi there,

Your issue appears to be describing the intended behavior of the software. If you want this to be changed, it would be a feature request. We recommend selecting "lock" to immediately lock your vault.

We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/

Please sign up on our forums (https://community.bitwarden.com/signup) and search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.

This issue will now be closed.

@cbw23 commented on GitHub (Sep 29, 2025): Hi there, Your issue appears to be describing the intended behavior of the software. If you want this to be changed, it would be a feature request. We recommend selecting "lock" to immediately lock your vault. We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/ Please sign up on our forums (https://community.bitwarden.com/signup) and search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked. This issue will now be closed.
GiteaMirror commented 2025-11-26 23:16:41 -06:00
Author
Owner
Copy Link

@jasttw commented on GitHub (Sep 29, 2025):

Thank you @cbw23 for your response.

Can you please explain the rationale of calling it exit and require confirmation to exit when all it does is send the app to the background? I feel it provides a false sense of security.

On windows and Linux, exiting the app locks the vault. So I doubt this is the intended behavior.

Thanks again for your response and attention to the issue

@jasttw commented on GitHub (Sep 29, 2025): Thank you @cbw23 for your response. Can you please explain the rationale of calling it exit and require confirmation to exit when all it does is send the app to the background? I feel it provides a false sense of security. On windows and Linux, exiting the app locks the vault. So I doubt this is the intended behavior. Thanks again for your response and attention to the issue
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#2357
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?