-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contact Method – Received email twice when add new Contact Method #46723
Comments
Triggered auto assignment to @Julesssss ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
We think that this bug might be related to #vip-vsp |
@arosiclair @dangrous -- I see changes to Auth which seem a likely cause of this regression: https://github.com/Expensify/Auth/pull/11815 This other Web PR could be related Web-E PR, but I think this is less likely than the Auth PR above. |
I think this is a backend issue. it shouldn't block NewDot. I'm not going to remove the backend deploy blocker label, though, as it might be occurring in OldDot too. |
I'm pretty sure it's unrelated since we didn't change when or how many emails get sent. I'm also seeing duplicate magic code emails on the staging login page as well so there's something else going on: |
yeah i agree with @arosiclair, ours might change the template but wouldn't change the number of emails, as far as I can tell |
Ah, okay thanks for sharing. I'll keep looking. |
Current assignee @Julesssss is eligible for the DeployBlockerCash assigner, not assigning anyone new. |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
No C+ on this one so gonna close it out. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.16-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4808025
Email or phone of affected tester (no customers): applausetester+jp_e_category_2@applause.expensifail.com
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
Received one email Verify secondary email
Actual Result:
Validation code is expired. Received email twice: Verify secondary email and a Magic sign-in code
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6560129_1722594456613.Code.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: