Workspace - User does not see the "error message" when deleting a workspace

[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. Open the New expensify app
2. Sign into an account with the correct set up applausetester@applause.expensifail.com
3. Navigate to Settings
4. Disable the internet connection in the device
5. Tap on the 3 dots and select "Delete Workspace"
6. Confirm the modal to delete the workspace
7. Verify the workspace is now displayed with a strikethrough indicating it will be deleted when back online
8. Enable the internet connection in the device
9. Wait a few seconds for the app to update
10. Close the settings modal

Expected Result:

The user expects to see a red dot in the profile icon and display a message on the workspace with the error as "You cannot delete this workspace because it's set as the domain restricted one for a domain security group" that can be removed

Actual Result:

The user sees the red dot in the profile icon, however they can no longer see the deleted workspace after returning online and can not see the error message text.

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number: 1.2.23.7

Reproducible in staging?: Yes

Reproducible in production?: No

Email or phone of affected tester (no customers):

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

Notes/Photos/Videos: Any additional supporting documentation

Bug5805000_User_does_not_see_the_error_message_after_returning_online_and_the_worksapce_is_also_gone.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[kbecciv]

Issue is not reproduced in production

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

[roryabraham]

Guessing it's something to do with this PR

[roryabraham]

Going to snag this to see if we can get the deploy over the finish line today

[roryabraham]

Sign into an account with the correct set up

@kbecciv This is pretty vague. What is the "correct setup"?

[roryabraham]

Seems like a domain restricted policy is a requirement here, need to find out what that is...

[roryabraham]

Okay, I was able to reproduce this locally (albeit with a hack in the API layer)

[roryabraham]

Got a fix ready: #12460