Created workspace is not immediately reflected in LHN

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Click on ‘Profile’ avatar
2. Click on ‘Workspaces’ link
3. Click on ‘New workspace’ button
4. Observe that workspace is displayed on LHN briefly and disappeared

Expected Result:

Created workspace should be displayed on LHN upon creation

Actual Result:

Created workspace is not displayed on LHN upon creation

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 / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.9-4
Reproducible in staging?: y
Reproducible in production?: n
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
Notes/Photos/Videos: Any additional supporting documentation

2023-05-03.04.12.56.mp4

Recording.464.mp4

Expensify/Expensify Issue URL:
Issue reported by: @Natnael-Guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683076759095689

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0118b0a2d7058654a7
• Upwork Job ID: 1653811047192453120
• Last Price Increase: 2023-05-03

[MelvinBot]

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

[MelvinBot]

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.

[MelvinBot]

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

[flaviadefaria]

@robertjchen I'll leave this as hourly so that you can look into it as soon as possible.

[marcaaron]

Hmm I think this is maybe related to some backend change. I tried to reproduce this and what I see is:

If you turn off the "Use staging server" option in "Test preference" it will not be broken.

@joelbettner should get this on your radar as you are the web deployer this week. Once we deploy Web all NewDot versions will experience this issue.

[marcaaron]

https://expensify.slack.com/archives/C07J32337/p1683133905446709?thread_ts=1683131467.530349&cid=C07J32337

[marcaaron]

Removing the blocker since it is related to the Web deploy.

[MelvinBot]

Job added to Upwork: https://www.upwork.com/jobs/~0118b0a2d7058654a7

[MelvinBot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @Santhosh-Sellavel (Internal)

[melvin-bot]

@iwiznia, @flaviadefaria Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[iwiznia]

No update

[Natnael-Guchima]

Hello @iwiznia @flaviadefaria 👋. This issue seems to be fixed and deployed to production. I was testing it now, and it seems to be working fine.

2023-05-12.10.29.38.mp4

[Natnael-Guchima]

A gentle bump @iwiznia @flaviadefaria

[iwiznia]

@flaviadefaria I assume @Natnael-Guchima is asking for payment for reporting the bug

[flaviadefaria]

Paying him now!

[flaviadefaria]

Offer sent, waiting for it to be accepted so that I can you @Natnael-Guchima.

[Natnael-Guchima]

Offer sent, waiting for it to be accepted so that I can you @Natnael-Guchima.

Accepted. Thanks @flaviadefaria .

[flaviadefaria]

Paid so closing this!