Web - Workspace image change for a second while adding or removing user

[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. Create a workspace if not created
2. Go to Settings > Workspaces > Members
3. Click on invite button
4. Invite userB
5. Check the userB LHN

Expected Result:

Workspace image should not be change

Actual Result:

Workspace image change for a second while adding or removing user

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.43-2
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

Screen.Recording.2023-07-20.at.11.58.19.AM.mov

Recording.3773.mp4

Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689834584194399

View all open jobs on GitHub

[kbecciv]

Could be the same root cause of #23189, but correct me if I'm wrong! Thank you

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

[hannojg]

Double checking now @kbecciv

[hannojg]

Hmmmm, I can't reproduce that on main. In general I can tell that the U icon we are seeing, is because somewhere in the code the report name gets read as undefined.
Not sure if its even a bug caused by the PR to be honest.

[amyevans]

I can't repro on main either. Not sure if there's been App code merged since the last deploy to fix it, or maybe there's backend code that's on staging but not production yet 🤔

Continuing to investigate.

[amyevans]

I think it's probably this Web-E PR which separates pusher calls that were previously unified, any thoughts @iwiznia?

[amyevans]

Minor bug so not going to block the deploy on it.

[amyevans]

No update

[amyevans]

No update

[amyevans]

I don't think this one is worth fixing honestly, so I'm going to just close it