Email verification is not working, no One time passcode is being sent

[hari007sh]

Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
• I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

Tried logging in to my account but I don't see any otp being sent from warp

To reproduce

sign in again

Expected behavior

No response

Screenshots, videos, and logs

No response

Operating system (OS)

Linux

Operating system and version

ubuntu 26

Shell Version

No response

Current Warp version

No response

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[oz-for-oss]

@hari007sh

Here's what I found while triaging this issue:

This looks like a login/email-delivery failure, but there is not enough detail yet to tell whether the browser login flow failed before sending the passcode or whether the email was delayed/filtered. Please avoid posting your email address publicly; if this blocks account access, Warp support can handle private account-specific checks at support@warp.dev.

I have a few follow-up questions before I can narrow this down:

1. After entering your email in the browser login page, what exact message or state do you see? A screenshot with your email address hidden would help.
2. Which Warp version and channel were you using when you launched the sign-in flow from the app?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that linux login report where no OTP/passcode email arrives; likely auth/email-delivery related but currently underspecified..

Triage summary

The reporter is on Linux (Ubuntu 26) and cannot complete sign-in because no one-time passcode/OTP email arrives after trying to log in.

Evidence and likely area

• The report includes only a minimal repro ("sign in again") and does not include Warp version/channel, browser login-page state, screenshot, logs, or whether the browser flow reports that an email was sent.
• In the desktop client, sign-in/signup actions open Warp web auth URLs and then handle the returned auth redirect or pasted auth URL. The client-side paths I inspected do not send passcode emails directly.
• This makes area:auth the right routing label, but the current evidence is not enough to distinguish a client/browser-handoff failure from web auth/email-delivery or account-specific backend state.

Duplicate check

I enumerated all open issues and recently closed issues with gh api --paginate. One close related open issue exists (#13815, "Login page never send email"), but the dedupe workflow requires two or more likely duplicates before marking this issue duplicate, so duplicate_of is empty.

Suggested next step

Ask for the browser login-page state and Warp version/channel before treating this as a reproducible client-side bug. If the reporter cannot sign in and account/email details are needed, those details should be handled through Warp support rather than posted publicly.

Question reasoning

1. After entering your email in the browser login page, what exact message or state do you see? A screenshot with your email address hidden would help. — The client hands sign-in to a browser flow, so the visible browser state is needed to determine whether the flow claimed an email was sent, showed an error, or stalled before submission.
2. Which Warp version and channel were you using when you launched the sign-in flow from the app? — The report gives Linux/Ubuntu but not the Warp build, which is needed to correlate with current auth-flow behavior and recent fixes.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz