github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 19:39:41 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #4385] Passkeys regression - doesn't work when you try to authenticate with locked vault #21337

New Issue
Closed
opened 2026-04-16 21:46:05 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-16 21:46:05 -05:00
Owner
Copy Link

Originally created by @raywdude on GitHub (Nov 25, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/4385

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.
Originally created by @raywdude on GitHub (Nov 25, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/4385 ### 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 - [X] 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.
GiteaMirror added the bug label 2026-04-16 21:46:05 -05:00
GiteaMirror commented 2026-04-16 21:46:07 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Nov 25, 2024):

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

<!-- gh-comment-id:2498458731 --> @bitwarden-bot commented on GitHub (Nov 25, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-15372
GiteaMirror commented 2026-04-16 21:46:08 -05:00
Author
Owner
Copy Link

@IamSingh01 commented on GitHub (Nov 26, 2024):

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

<!-- gh-comment-id:2500977366 --> @IamSingh01 commented on GitHub (Nov 26, 2024): Yes, this is happening on the latest beta build available on github. I reinstalled the app from fdroid and now it's working fine.
GiteaMirror commented 2026-04-16 21:46:09 -05:00
Author
Owner
Copy Link

@raywdude commented on GitHub (Nov 26, 2024):

It's the latest play store release, 11.6.

<!-- gh-comment-id:2501001683 --> @raywdude commented on GitHub (Nov 26, 2024): It's the latest play store release, 11.6.
GiteaMirror commented 2026-04-16 21:46:10 -05:00
Author
Owner
Copy Link

@IamSingh01 commented on GitHub (Nov 26, 2024):

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

<!-- gh-comment-id:2501022854 --> @IamSingh01 commented on GitHub (Nov 26, 2024): > 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
GiteaMirror commented 2026-04-16 21:46:10 -05:00
Author
Owner
Copy Link

@cbbit commented on GitHub (Nov 26, 2024):

Hi there!

Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/android/issues/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!

<!-- gh-comment-id:2502012646 --> @cbbit commented on GitHub (Nov 26, 2024): Hi there! Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/android/issues/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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#21337
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?