Passkeys: mixed behaviour when using local cached copy (clients)

[ilbarone87]

I have my vaultwarden selfhosted only accessible from internal network, no tunnels no mesh vpn. Since the introduction of passkeys I knew that these can't be used with the local cached copy of the vault but you need to be able to contact the live vault to use the passkeys stored in there. Recently I've randomly discovered that this is not completely true, and they sometimes works for certain websites and not for others. Like for me it work for PayPal but not for GitHub.
Can someone help me to shed some light on this behaviour?
Thanks

[BlackDex]

This project is the Server side only. Specific client side items is not something we can answer correctly.

[dani-garcia]

Some older passkeys created by the Bitwarden clients used to have an internal counter that needs to be incrementing with each use, that means those passkeys need to sync the vault with each use to make sure they have the latest counter value. Newer versions of the clients don't have that counter anymore, which means they can be used offline.

What you're probably seeing is an older passkey with a counter that requires that sync. You can try to delete and recreate that passkey, and the newly created one should be usable offline.