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

BW locks when lock timeout has not expired #2115

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

Originally created by @RickPJ on GitHub (Jan 1, 2025).

Steps To Reproduce

Precise reproduction can be uncertain. Typical scenario:

  1. Open the BW app, unlock with fingerprint.
  2. Select a web login, and launch.
  3. Tap on autofill tile - BW asks for fingerprint again.
  4. Quite frequently, opening the app again from its launch icon once more requires fingerprint.
    Lock timeout is set to 5 minutes, but behaviour is the same regardless of timeout setting.

Expected Result

Once unlocked BW should remain unlocked until the timeout has expired, regardless of how it is opened.

Actual Result

As described above, BW keeps relocking. The behaviour intuitively suggests that the different methods of launching the app are not internally sharing the same lock status and timer, though this is probably a simplification of reality!

Screenshots or Videos

No response

Additional Context

No response

Build Version

2024.12.0 (19597)

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

FairPhone 3+, AOS 11

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 @RickPJ on GitHub (Jan 1, 2025). ### Steps To Reproduce Precise reproduction can be uncertain. Typical scenario: 1. Open the BW app, unlock with fingerprint. 2. Select a web login, and launch. 3. Tap on autofill tile - BW asks for fingerprint again. 4. Quite frequently, opening the app again from its launch icon once more requires fingerprint. Lock timeout is set to 5 minutes, but behaviour is the same regardless of timeout setting. ### Expected Result Once unlocked BW should remain unlocked until the timeout has expired, regardless of how it is opened. ### Actual Result As described above, BW keeps relocking. The behaviour intuitively suggests that the different methods of launching the app are not internally sharing the same lock status and timer, though this is probably a simplification of reality! ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2024.12.0 (19597) ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details FairPhone 3+, AOS 11 ### 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:31 -06:00
GiteaMirror commented 2025-11-26 23:08:31 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jan 1, 2025):

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

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

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

Hi, supporting this issue.
A simple way to test this issue is with login pages where you need first to add the email and then it loads a second page where you need to add the email.
https://accounts.google.com/ is a good testing case.

In such cases, Bitwarden first asks to login to fill the email, then it closes itself going back to the browser. The browser loads the next page and when Bitwarden has to fill also the password field, it requires once again to login.

@pasquale95 commented on GitHub (Jan 10, 2025): Hi, supporting this issue. A simple way to test this issue is with login pages where you need first to add the email and then it loads a second page where you need to add the email. https://accounts.google.com/ is a good testing case. In such cases, Bitwarden first asks to login to fill the email, then it closes itself going back to the browser. The browser loads the next page and when Bitwarden has to fill also the password field, it requires once again to login.
GiteaMirror commented 2025-11-26 23:08:32 -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! 🙏
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#2115
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?