[Due for payment 2026-06-01] [Due for payment 2026-05-29] Members - Contact list does not load when scrolled to the bottom of the list

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.79-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #91250
Email or phone of affected tester (no customers): applausetester+ssndjois2jd@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Log in with account that has a lot of contacts (Expensifail account).

1. Go to staging.new.expensify.com
2. Go to workspace settings > Members.
3. Click Invite member.
4. Scroll down to the bottom of the list.

Expected Result:

Contact list will load when scrolled to the bottom of the list.

Actual Result:

Contact list does not load when scrolled to the bottom of the list.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7160093_1779400076003.1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mkhutornyi

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #91250

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #91250 - "Stop scroll jump on workspace invite member selection" by @MelvinBot (High confidence)
Related Issues: #61414

Recommendation: REVERT

PR #91250 broke infinite-scroll/pagination on the Workspace Invite Members page. The fix introduces a subtle counter inconsistency and revering the PR is the safest path forward given the issue is only in staging.

Assigned: @MelvinBot (PR author), @mkhutornyi @francoisl (approving reviewers)
Labels: No label changes made — DeployBlockerCash is correctly present (this is a Frontend/App bug, no DeployBlocker label to remove).

Detailed Analysis

Evidence

• The issue reproduces on staging only (version 9.3.79-1) and not on production, meaning it was introduced in this staging cycle.
• melvin-bot immediately flagged PR Stop scroll jump on workspace invite member selection #91250 as the candidate on the issue.
• PR Stop scroll jump on workspace invite member selection #91250 was merged on 2026-05-21 and is listed in the StagingDeployCash for 9.3.79-1.
• The PR modifies src/pages/workspace/DynamicWorkspaceInvitePage.tsx and src/hooks/useSearchSelector/base.ts, both of which directly control the Workspace Members invite page and its contact list.

Verification

• Affected file: src/pages/workspace/DynamicWorkspaceInvitePage.tsx — the PR modifies this file, changing how contact list sections are built and adding shouldKeepSelectedInAvailableOptions: true.
• Shared hook: src/hooks/useSearchSelector/base.ts — the PR adds shouldSeparateNonExistingSelectedOptions logic and returns selectedNonExistingOptions.
• The PR is confirmed to touch both files central to the reported bug (infinite scroll on the invite member page).

Root Cause

The onListEndReached pagination function in useSearchSelectorBase (line ~351 of base.ts) decides whether to load more items by counting entries in baseOptions. baseOptions is built by calling getValidOptions with includeSelectedOptions: false, meaning selected contacts are excluded from the count.

Before this PR, the total number of items visible in the list matched what onListEndReached counted, because selected items were removed from the list and shown in a separate top section. After this PR introduced shouldKeepSelectedInAvailableOptions: true, selected contacts remain in the displayed filteredPersonalDetails list — but they are still excluded from baseOptions (because includeSelectedOptions: false was not changed).

The consequence is that baseOptions item count can fall below maxResults even when the displayed list is at capacity. The guard if (optionsCount < maxResults) { return; } fires prematurely, preventing maxResults from being incremented, so the next page of contacts is never loaded when the user scrolls to the bottom.