WebAuthn 2FA causes 'We were unable to process your request. Please try again or contact us'
roberto-sartori-gl opened this issue · comments
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.
Thank you for your report! We've added this to our internal board for review.
ID: PM-17814
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!