BW locks when lock timeout has not expired

[RickPJ]

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.

[bitwarden-bot]

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

[pasquale95]

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.