Skip to content
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

Passkeys regression - doesn't work when you try to authenticate with locked vault #4385

Closed
1 task done
raywdude opened this issue Nov 25, 2024 · 5 comments
Closed
1 task done
Labels

Comments

@raywdude
Copy link

raywdude commented Nov 25, 2024

Steps To Reproduce

  1. Open Bitwarden
  2. Make sure passkeys are enabled
  3. Open your browser of choice
  4. Open recent apps menu and swipe away the Bitwarden app
  5. Go to a passkey supported site and try to login using passkey
  6. Authenticate using biometrics

Expected Result

Authentication is successful

Actual Result

Bitwarden throws an error "passkey authentication failed because user could not be verified"

Screenshots or Videos

No response

Additional Context

No response

Build Version

2024.11.6

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Samsung s24 ultra (sm-s928u1)

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@raywdude raywdude added the bug label Nov 25, 2024
@bitwarden-bot
Copy link

Thank you for your report! We've added this to our internal board for review.
ID: PM-15372

@singh9596
Copy link

Yes, this is happening on the latest beta build available on github. I reinstalled the app from fdroid and now it's working fine.

@raywdude
Copy link
Author

It's the latest play store release, 11.6.

@singh9596
Copy link

It's the latest play store release, 11.6.

Version 2024.11.3. install this version for the passkey or wait for the dev team to release an update with fix

@cbbit
Copy link

cbbit commented Nov 26, 2024

Hi there!

Thank you for your report, it seems like it is a duplicate of this one #4239

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these.

This issue will now be closed.

Thanks!

@cbbit cbbit closed this as not planned Won't fix, can't repro, duplicate, stale Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants