Passkey request disappears if I need to re-input master password

[jtaseff-gfms]

Steps To Reproduce

1. Bitwarden idle for long enough that it will prompts for master password the next time you use it
2. Go to a website that has a passkey registered
3. Try to use the passkey
4. Bitwarden prompts for master password
5. Bitwarden goes to the main view without being able to use the passkey

Expected Result

In previous versions, this would still pop up the confirmation box to use the passkey after logging in

Actual Result

After inputting master password, Bitwarden goes to the main view without being able to use the passkey

Screenshots or Videos

No response

Additional Context

No response

Operating System

Windows

Operating System Version

Windows 11

Web Browser

Firefox

Browser Version

No response

Build Version

2024.12.2

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 reporting this issue! We've added this to our internal tracking system.
ID: PM-16276

[toprowtech]

I am having this trouble as well. When logging into Google Gmail (for example) with a passkey. If the extension vault is locked, the extension requests unlock via Hello, PIN or password, etc., once the vault is unlocked, the extension shows items from the vault. It does not offer the Passkey.

If the vault is unlocked, the passkey is presented correctly.

I can reproduce this behavior on two different Windows 11 Pro computers. Google Chrome with extension version 2024.12.2.

Previously to 2024.12.2, the passkey would be presented after unlocking the vault as expected.

[rcmdkick]

Hey!

I have the same annoying issue. Already written the behaviour, but on Windows 10 Pro.

[jtodddd]

Hi there,

This issue has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

[toprowtech]

I went to create a screencast showing the behavior today and found that with Chrome extension 2024.12.3, the passkey behavior worked as it should.

I tested with another profile that still had extension 2024.12.2 and the passkey behavior when the vault was locked did not work correctly (it functioned as described above). However, I then updated that profile to extension 2024.12.3 and it did work correctly.

In short, this issue may have been resolved in the latest update 2024.12.3.