On my Chromebook until sometime recently whenever I try to “Verify it’s you” when logging into Google Bitwarden would initiate a Bluetooth conversation with my Pixel 9 during which I could select the built-in passkey on the phone, authenticate using my fingerprint and be done with it. Sometime recently it stopped doing the Bluetooth conversation and is now prompting me to scan a QR code every time before I can then authenticate. I find this highly annoying and want to restore the old behavior. Ideas?
I highly doubt, Bitwarden would initiate that. As far as I know, Bitwarden can’t even initiate that - it’s the OS or browser, I would think.
Which browser are you using?
As very recently discussed (Support "Device-Bound" Passkeys), this is something Bitwarden can’t do at the moment.
The QR code “thing” is also something, Bitwarden can’t do at the moment (hence this open feature request: Support for passkey QR codes / CDA (Cross-Device Authentication))
So, to me it seems, that Bitwarden doesn’t play a role in your issue… And I don’t know Chromebooks well enough, to be able to say anything else to that…
PS: Do you even see the Bitwarden passkey-window popping up? (like you can see here in the Help Sites) – That would indicate, Bitwarden would be involved…
This recent comment suggests otherwise:
Chrome on ChromeOS. I saw a different QR code window show up. I just assumed it was BitWarden’s but I guess it was ChromeOS so I will pursue it a long those lines.
The automatic Bluetooth prompt from your Pixel may stop working if your Chromebook and phone are no longer linked under “Connected Devices” or if Bluetooth/Nearby Share is off on either device. Try re-linking them and ensuring those features are enabled.