[Due for payment 2025-09-17] Reports - Expense report is missing name and avatar and not clickable for a specific account

[jponikarchuk]

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.2.2-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exploratory
Email or phone of affected tester (no customers): applausetester+khcategory19@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: All environment
App Component: Search

Action Performed:

1. Go to staging.new.expensify.com
2. Log in to this account - applausetester+khcategory19@applause.expensifail.com
3. Go to Reports > Reports.
4. Scroll down until there is an expense report with no name and no avatar.
5. Click on the expense report.

Expected Result:

Expense report will have report name and avatar and can be opened.

Actual Result:

Expense report does not report name and avatar and cannot be opened.

Account - applausetester+khcategory19@applause.expensifail.com
Report link - https://staging.new.expensify.com/r/8987667581269246
Report ID - R00fA8vWo2uM
Long ID - 8987667581269246

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @isabelastisser

[melvin-bot]

Triggered auto assignment to @isabelastisser (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]

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

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

[francoisl]

Any luck with this one @jasperhuangg? Do we need to open externally to help find the issue?

[jasperhuangg]

Ah thanks for the bump, looking now, sorry haven't had a chance to investigate this yet

[jasperhuangg]

@BlameGPT can you take a look