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

[PM-24264] Verification emails don't arrive #2299

New Issue
Open
opened 2025-11-26 23:14:54 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-26 23:14:54 -06:00
Owner
Copy Link

Originally created by @tejeszacsko on GitHub (Jul 29, 2025).

Steps To Reproduce

  1. When trying to log in either with
  • the master password or
  • the app authentication (through the Windows app)
  1. and successfully entering the password or authorising login in the Windows app
  2. 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

  • 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 @tejeszacsko on GitHub (Jul 29, 2025). ### Steps To Reproduce 1. When trying to log in either with - the master password 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.
GiteaMirror added the app:password-managerbug labels 2025-11-26 23:14:54 -06:00
GiteaMirror commented 2025-11-26 23:14:55 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jul 29, 2025):

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

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

@Adedamola-Aina commented on GitHub (Jul 30, 2025):

Hello @tejeszacsko

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.

@Adedamola-Aina commented on GitHub (Jul 30, 2025): Hello @tejeszacsko 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.
GiteaMirror commented 2025-11-26 23:14:55 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Oct 3, 2025):

The issue here will be closed.

@Adedamola-Aina This issue was not closed...

@pamperer562580892423 commented on GitHub (Oct 3, 2025): > The issue here will be closed. @Adedamola-Aina This issue was not closed...
GiteaMirror commented 2025-11-26 23:14:55 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Oct 3, 2025):

@Adedamola-Aina @david-livefront Is this: https://github.com/bitwarden/android/pull/5900 a fix for this issue here?

@pamperer562580892423 commented on GitHub (Oct 3, 2025): @Adedamola-Aina @david-livefront Is this: https://github.com/bitwarden/android/pull/5900 a fix for this issue here?
GiteaMirror commented 2025-11-26 23:14:56 -06:00
Author
Owner
Copy Link

@david-livefront commented on GitHub (Oct 3, 2025):

@Adedamola-Aina @david-livefront Is this: #5900 a fix for this issue here?

@pamperer562580892423 That PR updates the error message displayed to give users a better idea of why the request to resend the code is failing but does not resolve the issue. There will be future work required to handle the root problem.

@david-livefront commented on GitHub (Oct 3, 2025): > [@Adedamola-Aina](https://github.com/Adedamola-Aina) [@david-livefront](https://github.com/david-livefront) Is this: [#5900](https://github.com/bitwarden/android/pull/5900) a fix for this issue here? @pamperer562580892423 That PR updates the error message displayed to give users a better idea of why the request to resend the code is failing but does not resolve the issue. There will be future work required to handle the root problem.
GiteaMirror commented 2025-11-26 23:14:56 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Oct 3, 2025):

@david-livefront Ok, thank you for that explanation!

@pamperer562580892423 commented on GitHub (Oct 3, 2025): @david-livefront Ok, thank you for that explanation!
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 app:password-manager 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#2299
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?