[$500] Invite members - blank row is displayed when removing user in offline mode

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: v1.4.44-0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team

Action Performed:

1. Navigate to 'Invite members' page of a workspace
2. Invite a user
3. Apply offline mode
4. Removed the user

Expected Result:

There shouldn't be any blank rows

Actual Result:

There is a blank row after removing the user

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6393370_1708984795561.Screen_Recording_2024-02-27_at_12.21.52_at_night.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01b21db9a428272553
• Upwork Job ID: 1762247192499994624
• Last Price Increase: 2024-02-26

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01b21db9a428272553

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (External)

[github-actions]

👋 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 @aldo-expensify (Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[kbecciv]

We think that this bug might be related to #wave8-collect-admins
CC @zanyrenney

[ZhenjaHorbach]

I think it's dupe and should be fixed in one PR
Different actual result
But we expect the same result
#37109

[luacmartins]

This is a dupe of #37109. Gonna close since it's known and we're working on fixing it when we implement the remove functionality in Simplified Collect.