github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-09 11:44:41 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

WebAuthn 2FA causes 'We were unable to process your request. Please try again or contact us' #2160

New Issue
Closed
opened 2025-11-26 23:10:35 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-26 23:10:35 -06:00
Owner
Copy Link

Originally created by @roberto-sartori-gl on GitHub (Jan 31, 2025).

Steps To Reproduce

  • Install Bitwarden 2025.1 from Play Store
  • Open the app
  • Enter username/password
  • Proceed with the WebAuthn authentication procedure using an NFC Yubikey (FIDO2)
  • After this, we are back to the bitwarden app with the 'We were unable to process your request. Please try again or contact us' message and the login fails

Expected Result

My vault to load and show stored credentials

Actual Result

Cannot login

Screenshots or Videos

No response

Additional Context

I have a yubikey which I use as 2fa to login on bitwarden. It has worked fine until today, but nowI get the error message above whenever I try to login to the Android app.

  • 2FA on Chrome (Windows) works fine using WebAuthn with the same yubikey
  • 2FA via mail works fine on Android, but it is less secure compared to the yubikey
  • I already tried to uninstall and reinstall the Android app, without success.

Build Version

2025.1

What server are you connecting to?

Self-host

Self-host Server Version

2025.1.1 unified

Environment Details

Android 15, January 5, 2025 patches

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 @roberto-sartori-gl on GitHub (Jan 31, 2025). ### Steps To Reproduce - Install Bitwarden 2025.1 from Play Store - Open the app - Enter username/password - Proceed with the WebAuthn authentication procedure using an NFC Yubikey (FIDO2) - After this, we are back to the bitwarden app with the 'We were unable to process your request. Please try again or contact us' message and the login fails ### Expected Result My vault to load and show stored credentials ### Actual Result Cannot login ### Screenshots or Videos _No response_ ### Additional Context I have a yubikey which I use as 2fa to login on bitwarden. It has worked fine until today, but nowI get the error message above whenever I try to login to the Android app. - 2FA on Chrome (Windows) works fine using WebAuthn with the same yubikey - 2FA via mail works fine on Android, but it is less secure compared to the yubikey - I already tried to uninstall and reinstall the Android app, without success. ### Build Version 2025.1 ### What server are you connecting to? Self-host ### Self-host Server Version 2025.1.1 unified ### Environment Details Android 15, January 5, 2025 patches ### 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 2025-11-26 23:10:35 -06:00
GiteaMirror commented 2025-11-26 23:10:36 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jan 31, 2025):

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

@bitwarden-bot commented on GitHub (Jan 31, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-17814
GiteaMirror commented 2025-11-26 23:10:36 -06:00
Author
Owner
Copy Link

@jtodddd commented on GitHub (Jan 31, 2025):

Hi there,

I attempted to reproduce your issue and was unable to do so.

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!

@jtodddd commented on GitHub (Jan 31, 2025): Hi there, I attempted to reproduce your issue and was unable to do so. We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/). You can include a link to this issue in the message content. Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/). The issue here will 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#2160
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?