[Due for payment 2026-01-28] [$500] Full story : Clicking Certain Expense Reports Leads to NotFound — Reports Linked to Greyed-Out Submitter Avatars

[m-natarajan]

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:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @trjExpensify
Slack conversation (hyperlinked to channel name): #Quality

Action Performed:

1. Go to Reports in NewDot
2. Locate a report where the submitter’s avatar is greyed out
3. Click the report
4. Observe that it redirects to a NotFound page
5. Repeat with a report from a user whose avatar is not greyed out
6. That report opens successfully.

Expected Result:

All accessible reports should open normally regardless of the submitter’s avatar state.
Users should never see a NotFound page for reports they are permitted to view.

Actual Result:

Clicking reports from submitters with grey avatars leads to NotFound.
Clicking reports from submitters with normal avatars works as expected.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

The video for the issue is in OP

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022006354458176473216
• Upwork Job ID: 2006354458176473216
• Last Price Increase: 2026-01-07

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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.

[samranahm]

Proposal

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

Clicking Certain Expense Reports Leads to NotFound — Reports Linked to Greyed-Out Submitter Avatars

What is the root cause of that problem?

Reports with inaccessible submitters (indicated by greyed-out avatars due to missing personal details) are being displayed in the LHN despite having errorFields.notFound. Current logic allowed these reports to appear in the list when they had errors other than failed receipts, but excluded them only when displaying errors. When users clicked these reports, the canAccessReport function correctly identified them as inaccessible due to the notFound error flag and triggered the NotFound page.

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

We should prevents reports with notFound errors from appearing in the report list, to ensuring users cannot click on reports they don't have permission to access. Add an early return check for isReportInAccessible

if (isReportInAccessible) {
    return {shouldDisplay: false};
}

above here

App/src/libs/SidebarUtils.ts

Lines 205 to 208 in e5b83fc

	// Handle reports with errors
	if (hasErrorsOtherThanFailedReceipt && !isReportInAccessible) {
	return {shouldDisplay: true, hasErrorsOtherThanFailedReceipt: true};
	}

What alternative solutions did you explore? (Optional)

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.

[melvin-bot]

@mallenexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[mallenexpensify]

Added to Hot Pick, if it's not picked up soon I'll post in #external-backend-contributors

[melvin-bot]

@mallenexpensify Eep! 4 days overdue now. Issues have feelings too...