[$250] Workspace - User selection is not cleared when reopening invite list from workspace profile

[mitarachim]

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: 9.0.79-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.0
App Component: Workspace Settings

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace settings > Members.
3. Click Invite member.
4. Select another member > Next.
5. Close invite message page without inviting by clicking outside the RHP.
6. Click Invite member again.
7. Note that the previous selection is cleared.
8. Go to Workspace profile.
9. Click Invite.
10. Select another member > Next.
11. Close invite message page without inviting by clicking outside the RHP.
12. Click Invite member again.

Expected Result:

The selection should be cleared.

Actual Result:

The selection is not cleared.
This issue only happens with the Invite button on Workspace profile page.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6702809_1735286578549.20241227_155657.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021872610413601367629
• Upwork Job ID: 1872610413601367629
• Last Price Increase: 2024-12-27

Issue Owner

Current Issue Owner: @parasharrajat

[melvin-bot]

Triggered auto assignment to @techievivek (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @anmurali (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

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

[daledah]

Proposal

Please re-state the problem that we are trying to solve in this issue.

The selection is not cleared.
This issue only happens with the Invite button on Workspace profile page.

What is the root cause of that problem?

When navigating to invite member page in step 2, we had the logic to clear members

App/src/pages/workspace/WorkspaceMembersPage.tsx

Line 564 in e94df0f

onPress={inviteUser}

App/src/pages/workspace/WorkspaceMembersPage.tsx

Lines 209 to 212 in e94df0f

	const inviteUser = () => {
	clearInviteDraft();
	Navigation.navigate(ROUTES.WORKSPACE_INVITE.getRoute(route.params.policyID, Navigation.getActiveRouteWithoutParams()));
	};

but we don't do that in

App/src/pages/workspace/WorkspaceProfilePage.tsx

Line 354 in e94df0f

onPress={() => Navigation.navigate(ROUTES.WORKSPACE_INVITE.getRoute(route.params.policyID, Navigation.getActiveRouteWithoutParams()))}

What changes do you think we should make in order to solve the problem?

We should move this logic here to util function and use it in

App/src/pages/workspace/WorkspaceProfilePage.tsx

Line 354 in e94df0f

onPress={() => Navigation.navigate(ROUTES.WORKSPACE_INVITE.getRoute(route.params.policyID, Navigation.getActiveRouteWithoutParams()))}

and

App/src/pages/workspace/WorkspaceMembersPage.tsx

Line 564 in e94df0f

onPress={inviteUser}

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

NA

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[techievivek]

Demoting it since it's not deemed to be a deploy blocker.

[melvin-bot]

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

[melvin-bot]

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

[parasharrajat]

Reviewing...

[parasharrajat]

@daledah's proposal looks good to me. I don't think this change warrants a util function. We should be good to use the clearInviteDraft on the profile page too.

🎀 👀 🎀 C+ reviewed

[melvin-bot]

Current assignee @techievivek is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new.