github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-08 21:10:40 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #3314] FIDO2 WebAuthn 2FA flow on Android is loading 2 requests at the same time, and that is causing the authentication to fail. #7930

New Issue
Closed
opened 2026-04-11 00:41:06 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-11 00:41:06 -05:00
Owner
Copy Link

Originally created by @SergeantConfused on GitHub (Jun 10, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/3314

Steps To Reproduce

  1. Launch Bitwarden and enter your email address and master password.
  2. Tap on (Authenticate WebAuthn).
  3. Tap on (Use a difference device).
  4. Tap on (NFC security key).
  5. Place the FIDO2 WebAuthn Security Key on the phone.

Expected Result

To log into your individual Bitwarden account.

Actual Result

You are returned to the FIDO2 WebAuthn stage and you have a (Try Again) button, but pressing on that and performing the process again does not assist.

Screenshots or Videos

N/A.

Additional Context

If you tap on the (Back) button within the operating system at the point where you're returned to the FIDO2 WebAuthn stage with the (Try again) button, you'll see that the same stage is shown again; It seems like the Android client is loading that stage twice. In order to log in, you'd need to enter your email address and master password, and then dismiss the browser window that's launched for the FIDO2 WebAuthn flow, tap on (Back), and then on (Try again) and to then authenticate via FIDO2 WebAuthn.

Operating System

Android

Operating System Version

12

Device

Samsung Note10+

Build Version

2024.5.1

Beta

  • Using a pre-release version of the application.
Originally created by @SergeantConfused on GitHub (Jun 10, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/3314 ### Steps To Reproduce 1. Launch Bitwarden and enter your email address and master password. 2. Tap on (Authenticate WebAuthn). 3. Tap on (Use a difference device). 4. Tap on (NFC security key). 5. Place the FIDO2 WebAuthn Security Key on the phone. ### Expected Result To log into your individual Bitwarden account. ### Actual Result You are returned to the FIDO2 WebAuthn stage and you have a (Try Again) button, but pressing on that and performing the process again does not assist. ### Screenshots or Videos N/A. ### Additional Context If you tap on the (Back) button within the operating system at the point where you're returned to the FIDO2 WebAuthn stage with the (Try again) button, you'll see that the same stage is shown again; It seems like the Android client is loading that stage twice. In order to log in, you'd need to enter your email address and master password, and then dismiss the browser window that's launched for the FIDO2 WebAuthn flow, tap on (Back), and then on (Try again) and to then authenticate via FIDO2 WebAuthn. ### Operating System Android ### Operating System Version 12 ### Device Samsung Note10+ ### Build Version 2024.5.1 ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2026-04-11 00:41:06 -05:00
GiteaMirror commented 2026-04-11 00:41:08 -05:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/3314

<!-- gh-comment-id:2181379386 --> @vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/3314
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#7930
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?