Open danielhass opened 2 months ago
Thank you for your report! We've added this to our internal board for review. ID: PM-11231
This is seen not just in self hosted but also in bitwarden instance.
I had logged in with 2fa using previous version and updated to latest 2024.8.0.
No issues so far but upon clear data and then trying to login fails and 2fa verification .
Hi there,
This has been escalated for further investigation. If you have more information that can help us, please add it below.
Thanks!
I also had same issue. But I found workaround. If I tried login with other device, it accepts TOTP code. If I tried login with master password, it rejects.
I can confirm that 2FA login is also broke for me and am unable to independently login. The above workaround of approving the login from another device is the only way to access my vault on Android.
App version: 2024.8.0 (18985) Android OS: 14
Can confirm the most recent beta release 2024.8.0 broke 2FA Device: Samsung Galaxy S23 Ultra Android version: 14 / One UI version: 6.1 2FA: Google Authenticator
Troubleshooting steps:
"An error has occurred: Invalid verification code"
UPDATE: I have some more info that may help in isolating the issue: I noticed that when I added 'Email' as a 2FA method, and used the 3-dots menu in the App to switch to 'Email' verification during the 2FA step, the code I was sent (after several failed attempts to send) also resulted in this same "An error has occurred: Invalid verification code" pop-up message.
This would indicate the issue is within the App itself and it not handling the verification of the 2FA code correctly, and not related to the specific 2FA method being used. This is an important distinction here as I also get an email notification for a new login when I enter the correct code. This means App is saying "bad" but auth server is saying "good."
This also affects both the F-droid and non-F-droid beta builds equally.
This is my first time coming to Bitwarden Android's Github page for a bug, so I'm not familiar with typical turnaround times or prioritization here, but can we get any kind of update on this issue?
Are there any other specific logs or troubleshooting steps that would help aid in your investigation?
UPDATE: for anyone trying to rollback their Bitwarden app because this issue broke their app, here's what worked for me:
UPDATE 2: It looks like this has finally been fixed in 2024.8.1-beta (19099)
UPDATE 2: It looks like this has finally been fixed in 2024.8.1-beta (19099)
I can confirm that this issue is also fixed for me on 2024.8.1-beta (19099).
Bitwarden Beta
Steps To Reproduce
2024.8.0
beta app, select self-hosted and enter server URLAdditional context: I haven't seen any failing HTTP request or similar on my instance during the TOTP 2FA attempt.
Result: I'm unable to login into the Bitwarden app.
Expected Result
As I verified my TOTP via the web-based password manager of my instance I expect the login to work on mobile as well.
Actual Result
Login into Bitwarden app on self-hosted with TOTP 2FA not possible.
Screenshots or Videos
No response
Additional Context
No response
Build Version
2024.8.0 | Server: 2024.7.4
Environment Details
Issue Tracking Info