mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-05-23 08:32:45 -05:00
[GH-ISSUE #7094] Mobile 2FA broken: WebAuthn provider advertised with null data when no keys exist #19383
Reference in New Issue
Block a user
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?
Originally created by @korund on GitHub (Apr 13, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7094
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
1.35.6
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx/1.23.1 (Synology Web Station)
Host/Server Operating System
NAS/SAN
Operating System Version
Synology DSM 7.3.2-86009 Update 3
Clients
Android
Client Version
Bitwarden Android 2026.3.1 / 2025.12.1
Steps To Reproduce
DOMAINset (e.g.DOMAIN=https://example.com:8080)Expected Result
The app shows the TOTP code entry screen after entering the master password, same as the web vault and the official Bitwarden server (tested with bitwarden.eu).
Actual Result
The app shows an error dialog ("An error has occurred... contact us") with only a "Close" button. No 2FA prompt appears. After dismissing, the app stays on the password screen. The web vault works correctly with the same account and 2FA setup.
Logs
The Bitwarden Flight Recorder log shows:
-> app navigates back to password screen
The app receives the 400 response but does not recognize it as a 2FA challenge.
Vaultwarden response (
POST /identity/connect/token):bitwarden.eu response (same scenario — TOTP only, no WebAuthn keys):
Provider
8(WebAuthn) is present in the Vaultwarden response withnullchallenge data, despite no WebAuthn credentials in the database (SELECT * FROM twofactorshows only the TOTP record, atype=0). The official server does not include provider 8 in this scenario.Vaultwarden server log (
LOG_LEVEL=trace) during the failed mobile login:Server correctly returns the 2FA challenge. No follow-up request from the mobile client.
Screenshots or Videos
No response
Additional Context
Potentially relevant: #1471
@BlackDex commented on GitHub (Apr 13, 2026):
Should already be resolved via #7093 in v1.35.7.
@korund commented on GitHub (Apr 13, 2026):
That's a blazing fast fix! :D
Just checked with all the same inputs + VW 1.35.7. It works just fine. I confirm the resolution.
Thank you!