Repository navigation
Description
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.57-1
Reproducible in staging?: Needs reproduction (Unable to reproduce)
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: @PedroEspinoza1999
Slack conversation (hyperlinked to channel name): #Expensify Bugs
Action Performed:
- Log into New Expensify as an admin.
- Attempt to open a specific expense report.
- Observe the error message.
- Log into Expensify Classic.
- Navigate to the same report.
- Confirm that the report is visible and accessible in Classic.
Expected Result:
The admin should be able to access the same report in both Classic and New Expensify.
Report visibility and permissions should be consistent across platforms.
Actual Result:
In New Expensify, the admin receives the error: “Hmm... it's not here. This chat or expense may have been deleted or you do not have access to it.”
In Classic, the report is accessible without issues.
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 screenshot for the issue is in Slack thread
Issue Owner
Current Issue Owner: @francoislUpwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022042976567746112546
- Upwork Job ID: 2042976567746112546
- Last Price Increase: 2026-04-18
Metadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
MelvinBot commentedon Apr 11, 2026
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
MelvinBot commentedon Apr 11, 2026
Proposal
What is the root cause of that problem?
When a user navigates to a report in New Expensify, the
ReportFetchHandler(App/src/pages/inbox/ReportFetchHandler.tsx:102) callsopenReport(), which sends theOpenReportcommand to the backend. The backend checks whether the user has access to the report and, if access is denied, returns Onyx data that setserrorFields.notFoundon the report object. The frontend'scanAccessReport()(App/src/libs/ReportUtils.ts:9100-9111) then returnsfalse, andReportNotFoundGuard(App/src/pages/inbox/ReportNotFoundGuard.tsx:56) renders the "Hmm... it's not here" page.The likely discrepancy is in how the backend's
OpenReportcommand checks access vs. how Classic determines report visibility. In New Expensify, report access is participant-based —isReportParticipant()(App/src/libs/ReportUtils.ts:10733-10745) only considers users inreport.participants,ownerAccountID, andmanagerID. It does not account for workspace admins who aren't direct participants. In Classic, workspace admins can typically view all expense reports in their workspace regardless of participant status. If the backendOpenReportcommand uses a similar participant-only check, a workspace admin who isn't explicitly a participant/owner/manager of a specific expense report would getnotFound— even though Classic's broader policy-admin-aware visibility would show the same report.What changes do you think we should make in order to solve the problem?
The backend
OpenReportcommand's access check should grant access to workspace admins for expense reports within their workspace, matching Classic's behavior. The backend code would need to check the user's policy role (admin/owner) in addition to participant membership when determining access.On the frontend side, no changes should be needed — the frontend already defers to the backend's
errorFields.notFoundflag. Once the backend correctly grants access, the flag won't be set and the report will render normally.What alternative solutions did you explore? (Optional)
An alternative would be to add a frontend fallback that checks policy admin status before showing the not-found page — but this would be a workaround. The backend is the source of truth for access, so the fix should be there.
Investigation details
Error flow:
/r/REPORT_ID→ReportFetchHandlercallsopenReport()OpenReportchecks access → returnserrorFields.notFoundin Onyx data if deniedcanAccessReport()seeserrorFields.notFound→ returnsfalseReportNotFoundGuardshows "Hmm... it's not here" with subtitle "This chat or expense may have been deleted or you do not have access to it."Key code locations:
App/src/languages/en.ts:3386-3388App/src/libs/ReportUtils.ts:9100-9111(canAccessReport)App/src/libs/ReportUtils.ts:10733-10745(isReportParticipant)App/src/pages/inbox/ReportNotFoundGuard.tsx:56-61App/src/pages/inbox/ReportFetchHandler.tsx:102-126App/src/libs/actions/Report/index.ts:1326-1334Alternative explanations considered:
isLoadingbecomes false beforeOpenReportresponse arrives — unlikely sinceReportNotFoundGuardchecksisLoadingReportDatafromisLoadingAppand report metadata loading stateNext Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR,@MelvinBot <your feedback>to refine this analysis, or explain why you are rejecting Melvin's proposal.melvin-bot commentedon Apr 11, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee (
External)melvin-bot commentedon Apr 11, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022042976567746112546
[-]Admin unable to access report in New Expensify that is visible in Classic[/-][+][$250] Admin unable to access report in New Expensify that is visible in Classic[/+]github-actions commentedon Apr 11, 2026
ghmaimon commentedon Apr 11, 2026
Proposal
What is the root cause of that problem?
When an admin opens an expense report in NewDot, the backend's
OpenReportcommand only grants access if the user is a direct participant, owner, or manager of that report. If the admin doesn't match any of those, the backend returnserrorFields.notFound: true. The frontend then callscanAccessReport()inReportUtils.ts, sees that flag, and shows the "Hmm... it's not here" page.In Classic, workspace admins can access all expense reports belonging to their workspace regardless of direct participation. NewDot's backend check doesn't replicate this rule, which is the root cause.
What changes do you think we should make in order to solve the problem?
Two changes:
The backend
OpenReporthandler should grant access to policy admins and owners for reports in their workspace, the same way Classic does.In
canAccessReport()inReportUtils.ts, add a check so that if the current user is a policy admin for the report's workspace, thenotFoundflag is ignored and access is returned astrue. This keeps the frontend gate consistent with the backend fix and also unlocks report links inReportActionItemParentActionwhich uses the same function.What alternative solutions did you explore? (Optional)
withReportOrNotFoundandwithReportAndReportActionOrNotFounddirectly instead ofcanAccessReport— would need two separate changes instead of fixing the shared function.ReportNotFoundGuard— that component doesn't usecanAccessReport, so it wouldn't fix the actual screen gate.isAdminflag from the frontend in theOpenReportrequest — trusting a client-supplied privilege flag is a security risk.github-actions commentedon Apr 11, 2026
7 remaining items
github-actions commentedon Apr 13, 2026
jjcoffee commentedon Apr 13, 2026
Sounds like a BE issue based on Melv's analysis.
🎀👀🎀 C+ reviewed
melvin-bot commentedon Apr 13, 2026
Triggered auto assignment to @francoisl, see https://stackoverflow.com/c/expensify/questions/7972 for more details.
melvin-bot commentedon Apr 14, 2026
francoisl commentedon Apr 14, 2026
@Pereira-Fabiano Please do not post customer-identifying information in the App repo.
melvin-bot commentedon Apr 17, 2026
@francoisl Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
melvin-bot commentedon Apr 18, 2026
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
francoisl commentedon Apr 20, 2026
Can't reproduce in 2 different accounts that I tried, going to tentatively close. If it's still happening with a specific user's account, please open an internal issue with their details.
lndz-coli commentedon Apr 20, 2026
@francoisl I don't have the means to test this, but I provided a probable way to reproduce in my proposal
How to reproduce
Any interrupted
openReport()(network failure, tab backgrounded/closed mid-fetch, device sleep, 5xx, nav-away) leaves the stale fingerprint. QA misses it because test environments reset between runs.Steps (Chrome, network throttling):
${R}admin has access to but hasn't opened this session.${R}. Optimistic write fires, fetch fails, failureData writesisLoadingInitialReportActions: false. "Not here" shows (expected while offline)./r/${R}.openReport()optimistic write, then renders the report.