[Due for payment 2026-09-30] Spend - From filter is missing user when opened via View user history in public room

[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.4.91-2
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #99295
Email or phone of affected tester (no customers): jdonijsdonjsoindjsio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Search

Action Performed:

Precondition:

• As User A, create a public room, send a message in public room and copy the public room link.
• User B is logged out.
• Perform the steps below as User B:

1. Go to staging.new.expensify.com
2. Open the public room.
3. Click Sign in.
4. Enter new Gmail account and complete onboarding.
5. Click on User A avatar > View user history.
6. Open From filter.

Expected Result:

From filter will show User A in the list.

Actual Result:

From filter shows User A as selected, but User A is not shown in 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

Bug7266320_1790084702662.16.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @marufsharifi

[melvin-bot]

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

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

@Julesssss @marufsharifi you have been assigned to this deploy blocker because you reviewed the offending PR: #99295

[melvin-bot]

@hungvu193 you have been assigned to this deploy blocker because you authored the offending PR: #99295

[melvin-bot]

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