Unable to create account in applause.expensifail.com domain

[m-natarajan]

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: 1.4.68-3
Reproducible in staging?: y
Reproducible in production?: no
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

1. Go staging.new.expensify.com
2. Enter any email address which does not have expensify account in the domain applause.expensifail.com
3. Click continue

Expected Result:

Taken to entering magic code page

Actual Result:

Error message appears ""Cannot get account details, please try again or contact [concierge@expensify.com"]

NOTE: No issue with public domain gmail.com and sign in with existing applause.expensifail.com domain accounts

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6467147_1714509407793.bandicam_2024-04-30_22-32-38-959.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @hayata-suenaga (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @anmurali (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[github-actions]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[francoisl]

This may have been a temporary backend issue and seems to be working fine now, can you try again please?

If you're still running into an issue, please make sure to paste the email address you were using in comment too.

[francoisl]

Oh I see, you were using the domain applause.expensifail.com, not applause.expensify.com. Looks like it might be a backend issue, looking now.

[francoisl]

Yeah this is a backend issue, it's happening on OldDot as well. It only seems to be affecting applause.expansifail.com from what I can tell. Going to remove the blocker label for NewDot.