Cant receive verification code email

impossible_symmetry · October 3, 2025, 12:59pm

I’m trying to open the Bitwarden app on my Android device. After entering my master password, Bitwarden asks me to confirm my identity by entering an 8-digit code sent to my email. However, I’m not receiving any emails. Of course, I’ve checked my spam folder and tried logging in several times—this is my fourth attempt—but nothing works. Additionally, every time I click the “Send again” button, I get an error (stack trace below).

Stacktrace:retrofit2.HttpException: HTTP 401com.bitwarden.network.core.NetworkResultCall.toNetworkResult(r8-map-id-32def497a69cc50ae901b3596c8c5edea638a4bddea407cc5467c1b664832cc6:9)com.bitwarden.network.core.NetworkResultCall.access$toNetworkResult(r8-map-id-32def497a69cc50ae901b3596c8c5edea638a4bddea407cc5467c1b664832cc6:1)com.bitwarden.network.core.NetworkResultCall$enqueue$1.onResponse(r8-map-id-32def497a69cc50ae901b3596c8c5edea638a4bddea407cc5467c1b664832cc6:15)H3.e.x(r8-map-id-32def497a69cc50ae901b3596c8c5edea638a4bddea407cc5467c1b664832cc6:13)zd.m.run(r8-map-id-32def497a69cc50ae901b3596c8c5edea638a4bddea407cc5467c1b664832cc6:55)java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)java.lang.Thread.run(Thread.java:1119)

Version: 2025.9.0 (20692)Device: 📱 Redmi 23124RA7EO 🤖 15@35 📦 prodCI: 🧱 commit: bitwarden/android/release/2025.9-rc34@2bd4834b14d1e199aaa8a9ee4f0db812c27dba53💻 build source: bitwarden/android/actions/runs/17498992515/attempts/1

Moreover, I successfully registered on community.bitwarden and received my verification email without any issues.

grb · October 3, 2025, 3:11pm

I would suggest that you report this as a bug (“New Issue”) on Github, and/or contact Customer Support.

Are you using Microsoft Outlook for your email account, by any chance?

JLC · October 3, 2025, 5:16pm

Add me to that. Have contacted support too. My email is self hosted so no problem with spam.

For their diagnostics, I am getting automated emails from my support query to my email, so that’s working.

Nail1684 · October 3, 2025, 5:57pm

I think there already is a corresponding issue on GitHub:

github.com/bitwarden/android

[PM-24264] Verification emails don't arrive

opened 01:12PM - 29 Jul 25 UTC

tejeszacsko

bug app:password-manager

### Steps To Reproduce 1. When trying to log in either with - the master passwo…rd or - the app authentication (through the Windows app) 2. and successfully entering the password or authorising login in the Windows app 3. the app asks for the verification code that supposedly was just sent in email (2-step login enabled on the account with the email option) ### Expected Result The verification email with the code should be sent right after providing the master password or after authorising login through the Windows app, so when received, I can log back into the Android app. Furthermore, the app shouldn't fail to (re)send when using the [Send verification code email again] button. Also, I suspect that both of these problems could be caused by the same issue, but if I am right about this, at the first automatic attempt, **the app also fails to report** that it didn't manage to send the email in the first place - leaving the user with false hopes that it may arrive after some time. It should report failure right after the first failed attempt. ### Actual Result The verification email **never arrives** to my email address (while, if I try logging into the Web Vault on my PC, the verification email is received straight away and I can log in there). When I hit the [Send verification code email again] button, there seems to be a problem every time; a pop-up message titled "An error has occurred." appears with the message: > Could not send verification email. Try again. and there are two options to choose from on this pop-up: - Share error details - OK By selecting the "Share error details" option, the following output is provided: `Stacktrace: retrofit2.HttpException: HTTP 400 com.bitwarden.network.core.NetworkResultCall.toNetworkResult(Unknown Source:10) com.bitwarden.network.core.NetworkResultCall.access$toNetworkResult(Unknown Source:0) com.bitwarden.network.core.NetworkResultCall$enqueue$1.onResponse(Unknown Source:14) w3.l.q(Unknown Source:12) ud.f.run(Unknown Source:46) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644) java.lang.Thread.run(Thread.java:1012)` `Version: 2025.6.1 (20398) Device: 📱 samsung SM-S928B 🤖 15@35 📦 prod CI: 🧱 commit: bitwarden/android/release/hotfix-v2025.6.0-bwpm@e8878d321546a846909c70c00cdf8d7071f0ecf0 💻 build source: bitwarden/android/actions/runs/15984517798/attempts/1` ### Additional Context I tried to log in yesterday a couple of times, also tried to use the resend option, which failed every time, so I gave up and thought I would try waiting; maybe the email will arrive after some time. Today, checking my emails, I found none from Bitwarden, so I tried again, but it still didn't work. Then I tried deleting both cache and app data, but even these didn't seem to help; only the login authorisation option through the Windows app disappeared, and the Master password became the only option to start with. After this, I tried removing the app completely, rebooting my phone, and reinstalling the app from scratch, but it was still all the same, no verification email, and failures only when requesting to resend. ### Build Version 2025.6.1 (20398) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Device: Samsung SM-S928B Galaxy S24 Ultra running with the latest Samsung fw (Android 15, One UI 7.0) ### 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.

impossible_symmetry · October 3, 2025, 6:06pm

Thanks! No I’m using Proton Mail

impossible_symmetry · October 3, 2025, 6:08pm

Thanks! So it seems the only option is to wait. Hope they’ll fix it soon

Nail1684 · October 3, 2025, 6:14pm

Hm, no. It seems you are subjected to the New Device Login Protection (NDLP). You can contact support and ask for temporary suspension of the NDLP to be able to login again.

And if you would set up 2FA (–> Why Use Two-Step Login? | Bitwarden) for your BW account/vault, then the NDLP would be deactivated (for as long as you don’t deactivate 2FA). – There are five 2FA options for Bitwarden: Two-Step Login Methods | Bitwarden

PS: If you do set up 2FA, don’t forget to add your 2FA recovery code to your emergency sheets.

grb · October 3, 2025, 6:28pm

My understanding is the automated Bitwarden emails have invalid DKIM hashes, which cause some email service providers to reject the messages.

Nail1684 · October 3, 2025, 6:43pm

One of the developers commented there that “There will be future work required to handle the root problem.” – maybe that’s DKIM…

rtouze · January 22, 2026, 8:39am

I have the same issue. My email provider kindly put these emails in the Spam folder.

Nail1684 · January 22, 2026, 12:05pm

@rtouze Welcome to the forum!

So, you do receive these emails…?

rtouze · January 22, 2026, 1:28pm

Yes I do, in spam folder (sorry, I haven’t been clear enough).

However if this is a misconfiguration of DKIM record on bitwarden.com, I think some email providers can silently reject the email.

Sheep123 · January 24, 2026, 4:21pm

Same here I can’t login because the verification times out before the email is received. There are others with this issue as well Reddit - The heart of the internet

Nail1684 · January 24, 2026, 5:11pm

@Sheep123 Of course, the best thing would be if the emails could just be received in all cases. But apart from that, there are two possible scenarios for you and both should be solvable:

Scenario 1

If you see a prompt that say “We don’t recognize this device.” – like this one:

… then you are subjected to the “New Device Login Protection” (NDLP). And in that case, you can contact Bitwarden support, describe them your situation, and request to temporarily suspend the NDLP for your account.

(Then you are able to log in again – and it would be recommended to set up 2FA then. Don’t forget, to write down your 2FA recovery code on your emergency sheets.)

Scenario 2

If you’re seeing this prompt instead:

… without the text “We don’t recognize your device.”, then you set up email-2FA at one point in time. And now would be the perfect time to use your 2FA recovery code to deactivate all your 2FA options to be able to log in again.

(after that, you would be subjected to NDLP automatically, until you set up 2FA again… When you set up 2FA again: don’t forget, to write down your 2FA recovery code on your emergency sheets)