Workspace creation - 'Hmm... it's not here' in NewDot after workspace creation under OldDot

[dangrous]

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.3.96-6
Reproducible in staging?: Yes [BUT NOT ON main]
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: https://github.com/Expensify/Expensify/issues/334523
Issue reported by:
Slack conversation:

Action Performed:

Break down in numbered steps

Prerequisites: Must log out from OldDot and NewDot

1. Go to staging.expensify.com
2. Create a new Gmail account
3. Go to staging.expensify.com/pricing
4. Choose "Start" under the Free plan option
5. Confirm that you're redirected to NewDot
6. Verify that you're already logged in and directed to the Edit Workspace modal

Expected Result:

Describe what you think should've happened

User should be logged in and gets directed to the Edit Workspace modal in NewDot.

Actual Result:

Describe what actually happened

'Hmm... it's not here' showing up in NewDot after workspace creation under OldDot.

**Note: This seems to be fixed on main so it might be being handled under a separate bug. We might need to CP something though. cc @flodnv **

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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 [WILL TEST OTHERS IN A MOMENT]
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

281496039-9647deba-7d23-4f82-9602-2fbd9e359630.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @miljakljajic (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[OSBotify]

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

[melvin-bot]

Triggered auto assignment to @stitesExpensify (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[flodnv]

https://github.com/Expensify/Expensify/issues/334523#issuecomment-1802737093