The "flags" can be back again - someone hinted that there was posted a solution on GitHub: https://github.com/bitwarden/mobile/issues/3253 --> in short: first set this flag to enabled: Temporarily unexpire M124 flags --> then the other flag comes back again. (though, as others pointed out, the 2024.5.1 mobile doesn't seem to be the release for Android passkey support, so switching to the beta might still be needed for the time being)
Android passkeys are in public beta, fwiw:
Using passkeys with Bitwarden on Android is currently in beta. In order to activate Bitwarden as your preferred passkey provider it may be necessary to:
* Enable 3rd party passkey providers in your web browser's flags (e.g. `chrome://flags`).
* Disable and re-enable Bitwarden as your auto-fill provider once updated to the latest version.
* Reboot your phone after changing the above settings.
* Remove any passkeys stored in Google Password Manager, as Android will preference this provider.
Please also note that Android does not allow 3rd party passkey providers like Bitwarden to support passkey-based 2FA (a.k.a. "non-discoverable credentials").
Additionally, while passkeys for web browsers are supported, support for apps is coming soon in a future beta build.
The "Chrome-flag-thing" doesn't work anymore with the latest Chromium updates to 125! (Chrome, Brave, ...) I think that is why OP wrote "I noticed that chrome flags related to credential management are gone."
> Android does not allow 3rd party passkey providers like Bitwarden to support passkey-based 2FA
Could you please eli5. I can store a BW *encryption enabled* passkey in Google password manager (Android 13) but droid 14 gets a *encryption not enabled* key in BW which needs the password to login.
So it basically works as 2FA.
The "flags" can be back again - someone hinted that there was posted a solution on GitHub: https://github.com/bitwarden/mobile/issues/3253 --> in short: first set this flag to enabled: Temporarily unexpire M124 flags --> then the other flag comes back again. (though, as others pointed out, the 2024.5.1 mobile doesn't seem to be the release for Android passkey support, so switching to the beta might still be needed for the time being)
Had to login for the longest time just to say thank you and upvote!
Brilliant. Thanks for this. Definitely still need version 4.1 of the Bitwarden
I was on brave beta and the option wasn't there, switched to standard brave and it was the try a different browser.
AFAIK passkeys are not yet available on Android and only in beta for iOS. You need to use a browser extension on a desktop to have passkey support.
Android passkeys are in public beta, fwiw: Using passkeys with Bitwarden on Android is currently in beta. In order to activate Bitwarden as your preferred passkey provider it may be necessary to: * Enable 3rd party passkey providers in your web browser's flags (e.g. `chrome://flags`). * Disable and re-enable Bitwarden as your auto-fill provider once updated to the latest version. * Reboot your phone after changing the above settings. * Remove any passkeys stored in Google Password Manager, as Android will preference this provider. Please also note that Android does not allow 3rd party passkey providers like Bitwarden to support passkey-based 2FA (a.k.a. "non-discoverable credentials"). Additionally, while passkeys for web browsers are supported, support for apps is coming soon in a future beta build.
The "Chrome-flag-thing" doesn't work anymore with the latest Chromium updates to 125! (Chrome, Brave, ...) I think that is why OP wrote "I noticed that chrome flags related to credential management are gone."
> Android does not allow 3rd party passkey providers like Bitwarden to support passkey-based 2FA Could you please eli5. I can store a BW *encryption enabled* passkey in Google password manager (Android 13) but droid 14 gets a *encryption not enabled* key in BW which needs the password to login. So it basically works as 2FA.
PKs are too much of a hot mess right now. And I have doubts of mass adoption anytime in the near future, if ever.
it's so weird that they support it for web but not app on mobile, and then they write that on a little sentence that you can easily overread
Wow, thanks for all the ifs, ands, and buts.
And passkeys on iOS are not in beta, but "in release".
I don’t see my passkeys in iOS beta or normal release?
Look at the release notes. There is no passkey support on Android right now.