[HOLD for payment 2023-04-27] [HOLD for payment 2023-04-26] Workspace - When deleting a workspace offline. the layout breaks

[kbecciv]

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. Access staging.new.expensify.com
2. Sign into a valid account that is ready for Error tests
3. Turn off internet connection
4. Delete a workspace while offline

Expected Result:

User expects the layout to continue even when offline

Actual Result:

Layout breaks

Workaround:

Unknown

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

Reproducible in staging?: Yes

Reproducible in production?: No

If this was caught during regression testing, add the test name, ID and link from TestRail:

https://expensify.testrail.io/index.php?/runs/view/14829&group_by=cases:section_id&group_order=asc&group_id=229065

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[kbecciv]

Attaching TR picture to reproduce the issue

[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 @flodnv (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[flodnv]

Can confirm, I reproduced on staging web, but not on prod.

[flodnv]

I looked at the PRs in #17546, nothing stands out. I am going to use git bisect to find the offending PR, unless someone chimes in here: https://expensify.slack.com/archives/C01GTK53T8Q/p1681836208585709

[flodnv]

Reverting #17310 locally fixes it, so that PR caused it. Assigning everyone who was involved to decide what to do 🙃

[flodnv]

For some reason I cannot assign @akinwale