[Due for payment 2026-04-02] [Due for payment 2026-04-01] [RCA #77636] Expense - After leaving system message thread, account avatar changes to fallback avatar

[nlemma]

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.43-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #77636
Email or phone of affected tester (no customers): jiosdjnoisdjniojsdiosi@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense.
4. Open the report.
5. Click Amount.
6. Edit the amount and save it.
7. Hover over amount edit system message.
8. Click 3-dot menu > Leave thread.
9. Go to Account.

Expected Result:

After leaving system message thread, account avatar will not change to fallback avatar.

Actual Result:

After leaving system message thread, account avatar changes to fallback avatar.
Skeleton loader is shown next to fallback avatar.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7111847_1774365261283.3.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

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

[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: #77636 - "Part 1: Remove Onyx.connect() for the key: ONYXKEYS.PERSONAL_DETAILS_LIST in src/libs/actions/Report.ts" by @lorretheboy (High confidence)
Related Issues: None

Recommendation: REVERT

PR #77636 should be reverted to restore the correct behavior. The PR refactored openReport to require a personalDetails parameter but failed to update all call sites, causing the avatar to display as a fallback after leaving a thread.

Labels: No label changes needed. This is a frontend bug caused by an App PR, so DeployBlockerCash should remain.

📋 Detailed Analysis

Evidence

PR #77636 modified the openReport function to accept a personalDetails parameter (line 1309 in src/libs/actions/Report/index.ts). This parameter is optional in the type definition but critical for properly displaying user avatars.

The PR updated most call sites to pass personalDetails, but missed two critical locations in src/pages/inbox/ReportScreen.tsx:

1. Line 567: openReport({reportID: reportIDFromRoute, introSelected, reportActionID: reportActionIDFromRoute, betas});
2. Line 704: openReport({reportID, introSelected, betas});

Both calls are missing the personalDetails parameter.

Verification

I confirmed that:

1. PR Part 1: Remove Onyx.connect() for the key: ONYXKEYS.PERSONAL_DETAILS_LIST in src/libs/actions/Report.ts #77636 modified the openReport function signature to include personalDetails as a parameter
2. src/pages/inbox/ReportScreen.tsx does NOT retrieve or use personalDetails from Onyx
3. Line 704 is specifically triggered when a user returns to a thread after leaving it (see comment at line 699)
4. Without personalDetails, the openReport function cannot properly look up user avatar information, resulting in the fallback avatar being displayed
5. The bug is staging-only, matching the timeline when PR Part 1: Remove Onyx.connect() for the key: ONYXKEYS.PERSONAL_DETAILS_LIST in src/libs/actions/Report.ts #77636 was merged to staging

Root Cause

When a user leaves a thread and then navigates to another page (like Account), the ReportScreen component calls openReport without passing personalDetails. This causes the report to be opened without the necessary personal details data, which results in:

• Avatar data being unavailable or stale
• The avatar displaying as a fallback/default avatar
• A skeleton loader appearing next to the fallback avatar

The issue appears when navigating to Account because the ReportScreen useEffect at line 700-709 fires when the user returns to focus the app, attempting to rejoin the thread they just left - but it does so without the personal details, corrupting the avatar display state.