Fido2 is my only 2FA method … when logging in with a push notification to app or master password, I’m then presented with a screen with a button for “Authenticate WebAuthn”.
When click this blue button, I receive an error: “The authentication was cancelled or took too long.”
No combination of restarts or using other primary login methods changes the outcome.
I use Apple’s Keychain for managing my passkeys (including the one for Bitwarden)
macOS 15.3.2
BitWarden Version 2025.2.1 (38769)
In addition and perhaps related, I’m unable to to login to vault dot bitwarden dot com with my passkey (the POST https://vault.bitwarden.com/identity/connect/token results in a 400 … post body looks reasonable to me) but I’m able to use this same passkey as 2FA method when logging in on the web
@nefilim Welcome to the forum!
Did you only recently change to that? Because the desktop app on MacOS is only with version 2025.2.1 able to use FIDO2-2FA. - If you logged in previously to the desktop app the same way, then something doesn’t sound right here.
Anyway, did you try to deinstall and reinstall the desktop app? - A few hours ago, version 2025.3.0 was released, you could also download that one and see if it makes a difference.
Don’t ask me why Bitwarden still calls both “passkeys” (for 2FA and for full login) just “passkey”… But they are not the same credential - and a “login-with-passkeys”-passkey can’t be used as 2FA for Bitwarden - and vice versa, a 2FA-“passkey” can’t be used for “full login to Bitwarden”. (somehow this is meant as not to be confusing?!? 
)
Hey thanks @Nail1684! The distinction between the two types of passkeys weren’t readily apparent to me - I created one for logging in at vault.bitwarden.com 
I see a single Passkey entry for Bitwarden in macOS’ Password app and verified by logging out and logging back in with the Passkey (no 2FA required).
I then removed what I had for 2FA and reenabled it, left the name empty and click Read Key, created a second passkey for 2FA purposes. I still only see a single Passkey entry in macOS Password app.
Now I can no longer login with the Passkey (invalid grant error) but I can use it as 2FA when logging in with my master password. It’s hard to say with 100% certainty since Password app doesn’t show exact timestamps … but it looks like the Passkey entry is being overwritten in there by Bitwarden 
… then it seems the “Password app” can also - like Bitwarden - only store one “passkey” with an item. A workaround could be, to create a second “Bitwarden”-item in the passwords app for the other “passkey”-type.