Timeout is not honored when screen is locked

[Sedeniono]

Steps To Reproduce

1. Open the Bitwarden app.
2. Set the "Session timeout" to 1 minute (for ease of reproduction) and the session timeout action to "Lock".
3. Lock the screen of the phone (while the bitwarden app is still in the foreground) by pressing the device's power button to turn off the screen.
4. Wait more than 1 minute while the phone is locked.
5. Press the power button and unlock the phone via the phone's password/PIN/etc.
6. The bitwarden app is still in the foreground. The problem is: The vault is still unlocked, although the timeout period should have run out.

Expected Result

The bitwarden vault should be locked after the configured timeout passed, even if the phone itself got locked during the timeout period.

Actual Result

The bitwarden vault does not get locked.

Screenshots or Videos

No response

Additional Context

• If you do not lock the phone during the timeout period, but instead use some other apps, and then you go back to bitwarden, the vault is locked.
• You can also set a timeout of e.g. 5 or 15 minutes. The same thing happens: If the screen gets locked during this timeout period and you wait longer than the timeout, the vault remains unlocked.
• You can also "minimize" the bitwarden app before locking the phone. With "minimize" I mean to go to some other app or the home screen. The result is the same.
• If you first unlock the vault, then "minimize" the bitwarden app, then lock the phone for a few seconds, then unlock the phone, then wait for more than 1 minute without opening the bitwarden app, and then open the bitwarden app, the vault is locked.

=> To me it looks like the "timeout timer" in the bitwarden app gets paused as soon as the phone gets locked. And it gets resumed while the phone is unlocked.

Build Version

2024.11.7 (19528) from Google Play

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

Google Pixel 4a, Android 13, Build number TQ3A-230805.001.S1

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-15804

[Krychaz]

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!