Workspace - Infinite loading UI skeleton in invite new members after refresh

[izarutskaya]

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 settings then workspaces open any workspace
2. Click members then Invite to open the Invite new members page
3. refresh the page

Expected Result:

The suggested acounts should be displayed in the Invite new members page

Actual Result:

Infinite loading UI skeleton in invite new members after refresh

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: v1.3.58-1

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

Screencast.From.29-08-23.06.30.13.mp4

Recording.1358.mp4

Expensify/Expensify Issue URL:

Issue reported by: @Ahmed-Abdella)

Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1693280180858769

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @jliexpensify (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 @amyevans (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[aimane-chnaif]

Dupe of #22508

[Ahmed-Abdella]

Please note that the behavior in staging differs from production. In production the invite new members page is blank

[aimane-chnaif]

In production the invite new members page is blank

This is also bug. We should show skeleton

[amyevans]

Hmm I can't reproduce (tried on both staging and local)

Staging:

26196-staging.mov

Local:

26196-local.mov

@jliexpensify could you try as well? In any event, this shouldn't block deploy.

[aimane-chnaif]

This is interesting bug. Some people can reproduce but some people not. May depend on device, OS, browser versions.
Because of that, #22508 was closed, reopened and then closed again.
More details about the root cause: #22850 (comment)

[jliexpensify]

So this happened to me:

Here were my repro steps:

1. Open settings then workspaces open any workspace
2. Click out of New.Dot and into this GH
3. Click back into New.Dot tab and see it crash

So I couldn't even complete this the first time.

I tried again a second time, after refreshing, and wasn't able to reproduce. I think it's probably to do with general instability, since it's not always reproducible? cc @amyevans

[amyevans]

Okay thanks for giving it a shot. Regardless it seems pretty inconsistent and definitely an edge case. Given that, I don't think it's worth expending more effort on it at the moment, so going to close. Feel free to reopen though if you disagree @jliexpensify!