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

[GH-ISSUE #6245] [PM-29308] Can't authenticate with yubikey. An error has occurred. We were unable to process your request. #21662

New Issue
Closed
opened 2026-04-16 22:13:41 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-16 22:13:41 -05:00
Owner
Copy Link

Originally created by @Opening-Button-8988 on GitHub (Dec 7, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/6245

Steps To Reproduce

  1. Insert yubikey via USB-C.
  2. Open app
  3. Enter email address
  4. "Continue"
  5. Enter password. "Login in with master password".
  6. Wait ~10s for Authenticate WebAuthn page to appear.
  7. Launch WebAuthn.
  8. Default browser opens to page vault.bitwarden.com. Click "authenticate WebAuthn"
  9. Google prompt opens from the bottom of the screen, "No passkeys available". Click "use a different device"
  10. Google prompt now says "Connect your key". I tap the yubikey.
  11. Bitwarden opens and I see the error, "An error has occurred. We were unable to process your request. Please try again or contact us".

Expected Result

After step 9, I should have seen a prompt asking me to give the app permission to read data from the yubikey. It's a rectangle box that opens on the middle of the screen while the "connect your key" prompt is open.

Actual Result

I never received the usual prompt.

Screenshots or Videos

No response

Additional Context

I was attempting to report a bug related to a login delay, after this reading this: https://github.com/bitwarden/android/issues/4799#issuecomment-3612869059

As soon as I updated to 2025.11.0, I could no longer authenticate with my yubikey. The prompt that I explained was showing up on 2025.8.1, but it's no longer showing up. I can't remember exactly what the prompt said, but it was something like "Allow access to..." and contained some technical jargon related to authentication, most likely asking permission to read the yubikey. This is the prompt I see whenever I use my yubikey, on other apps like KeepassDX.

I tested NFC. The same error occurs.

Build Version

2025.11.0

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

  • Pixel 7
  • Android 16

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 @Opening-Button-8988 on GitHub (Dec 7, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/6245 ### Steps To Reproduce 1. Insert yubikey via USB-C. 2. Open app 3. Enter email address 4. "Continue" 5. Enter password. "Login in with master password". 6. Wait ~10s for Authenticate WebAuthn page to appear. 7. Launch WebAuthn. 8. Default browser opens to page vault.bitwarden.com. Click "authenticate WebAuthn" 9. Google prompt opens from the bottom of the screen, "No passkeys available". Click "use a different device" 10. Google prompt now says "Connect your key". I tap the yubikey. 11. Bitwarden opens and I see the error, "An error has occurred. We were unable to process your request. Please try again or contact us". ### Expected Result After step 9, I should have seen a prompt asking me to give the app permission to read data from the yubikey. It's a rectangle box that opens on the middle of the screen while the "connect your key" prompt is open. ### Actual Result I never received the usual prompt. ### Screenshots or Videos _No response_ ### Additional Context I was attempting to report a bug related to a login delay, after this reading this: https://github.com/bitwarden/android/issues/4799#issuecomment-3612869059 As soon as I updated to 2025.11.0, I could no longer authenticate with my yubikey. The prompt that I explained was showing up on 2025.8.1, but it's no longer showing up. I can't remember exactly what the prompt said, but it was something like "Allow access to..." and contained some technical jargon related to authentication, most likely asking permission to read the yubikey. This is the prompt I see whenever I use my yubikey, on other apps like KeepassDX. I tested NFC. The same error occurs. ### Build Version 2025.11.0 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Pixel 7 - Android 16 ### 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 app:password-managerbug labels 2026-04-16 22:13:41 -05:00
GiteaMirror commented 2026-04-16 22:13:42 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Dec 7, 2025):

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

<!-- gh-comment-id:3621944965 --> @bitwarden-bot commented on GitHub (Dec 7, 2025): Thank you for your report! We've added this to our internal board for review. ID: [PM-29308](https://bitwarden.atlassian.net/browse/PM-29308) [PM-29308]: https://bitwarden.atlassian.net/browse/PM-29308?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-16 22:13:42 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Dec 7, 2025):

Environment Details
Pixel 7
Android 16

Still GrapheneOS, like in your original issue?

PS: It might be helpful for Bitwarden, if you copy all available Environmental Details in here - for that, go to Settings --> About and tap on "Version: ..." in the BW Android app (that automatically copies it to the clipboard).

<!-- gh-comment-id:3622316199 --> @pamperer562580892423 commented on GitHub (Dec 7, 2025): > Environment Details > Pixel 7 > Android 16 Still GrapheneOS, like in your original issue? PS: It might be helpful for Bitwarden, if you copy all available Environmental Details in here - for that, go to Settings --> About and tap on "Version: ..." in the BW Android app (that automatically copies it to the clipboard).
GiteaMirror commented 2026-04-16 22:13:42 -05:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Dec 8, 2025):

Hello @Opening-Button-8988,

Thank you for this report. Could you please update to Bitwarden 2025.11.1, reboot the phone and let me know if you continue to encounter this? I tested this with a YubiKey 5C NFC on a Pixel 8 Pro with Android 16, and I was able to successfully log in using an email address, master password, and a FIDO2 WebAuthn Security Key 2FA over NFC and over USB with Bitwarden 2025.11.1.

If you continue to encounter this, I'd recommend creating a support ticket using the account's email address; also, you can send us the logs from Flight Recorder, which you can activate before logging in, as they may assist in finding the root cause of this.

I will close this GitHub report for now.

Thank you again,

<!-- gh-comment-id:3626902947 --> @SergeantConfused commented on GitHub (Dec 8, 2025): Hello @Opening-Button-8988, Thank you for this report. Could you please update to Bitwarden 2025.11.1, reboot the phone and let me know if you continue to encounter this? I tested this with a YubiKey 5C NFC on a Pixel 8 Pro with Android 16, and I was able to successfully log in using an email address, master password, and a FIDO2 WebAuthn Security Key 2FA over NFC and over USB with Bitwarden 2025.11.1. If you continue to encounter this, I'd recommend creating a [support ticket](https://bitwarden.com/help/) using the account's email address; also, you can send us the logs from [Flight Recorder](https://bitwarden.com/help/flight-recorder/), which you can activate before logging in, as they may assist in finding the root cause of this. I will close this GitHub report for now. Thank you again,
GiteaMirror commented 2026-04-16 22:13:43 -05:00
Author
Owner
Copy Link

@Opening-Button-8988 commented on GitHub (Dec 17, 2025):

@SergeantConfused

Thanks for the reply. I can confirm that after installing 2025.11.1 and rebooting, I am encountering this problem, but now I am getting the "Allow Google Play services access to Yubikey OTP+FIDO+CCID?" prompt where I previously wasn't. Also, I noticed something a little different (not sure if this is relevant). Normally when I get a prompt asking me to tap the key, the gold disk lights up repetitively. I tapped it once and nothing happened. Only after tapping a second time, after the lights on the key stopped flashing quickly, was I sent back to Bitwarden, where I again saw the error message.

I'll make a support ticket now as you suggested.

@pamperer562580892423 Apologies for that. Honestly, I left it out intentionally because I was afraid the issue might be dismissed. I should have said I was using GrapheneOS, sorry about that.

<!-- gh-comment-id:3663950757 --> @Opening-Button-8988 commented on GitHub (Dec 17, 2025): @SergeantConfused Thanks for the reply. I can confirm that after installing 2025.11.1 and rebooting, I am encountering this problem, but now I am getting the "Allow Google Play services access to Yubikey OTP+FIDO+CCID?" prompt where I previously wasn't. Also, I noticed something a little different (not sure if this is relevant). Normally when I get a prompt asking me to tap the key, the gold disk lights up repetitively. I tapped it once and nothing happened. Only after tapping a second time, after the lights on the key stopped flashing quickly, was I sent back to Bitwarden, where I again saw the error message. I'll make a support ticket now as you suggested. @pamperer562580892423 Apologies for that. Honestly, I left it out intentionally because I was afraid the issue might be dismissed. I should have said I was using GrapheneOS, sorry about that.
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 app:password-manager 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#21662
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?