-
Notifications
You must be signed in to change notification settings - Fork 819
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passkey support #4239
Comments
Thank you for your report! We've added this to our internal board for review. |
Same issue for me. I can login with passkeys, but I can't create them |
Duplicate of #3866, will close this one |
@Molenaar2 I think you should consider re-opening this issue - it is a more up to date description of the problem - my issue is a bit older, and so starts off describing an older issue, whereas yours describes what I believe to be the current issue - and the issues the Bitwarden team need to address:
|
Reopened as advised by @BJReplay |
Also having this issue - cannot login with my passkey. Worked in non-native but doesn't work in native. Have just the one passkey |
Also have this issue. One account, one passkey. Samsung S22U A14 - works in legacy but not native. |
Steps To Reproduce
I have two accounts for my UBank app, both accounts have a passkey defined. One account sits in my own vault, the other account sits in the organisation I belong to.
When I try to log in to the app, I get an error that the passkey operation failed, because the user could not be verified. In the previous non-native version of Bitwarden I got a pop-up showing the two passkeys (unfortunately not the user IDs!) and I could select the passkey/account I wanted to use. With the new native version, due to the error, I can no longer login.
Expected Result
Logged in to banking app
Actual Result
Error message that passkey operation failed because user could not be verified
Screenshots or Videos
My banking app doesn't allow to make screenshots
Additional Context
The non native version showed a pop-up with three two passkeys and I could select the one to be used (note, it showed the passkeys, unfortunately not the user IDs) Now in the native version it gives an error.
Build Version
2024.10.2
What server are you connecting to?
US
Self-host Server Version
No response
Environment Details
Samsung Galaxy A34
Android 14
Issue Tracking Info
The text was updated successfully, but these errors were encountered: