[$250] [Exploratory] Report details - Not found page opened when clicking admin report header

[applause-bot]

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: v9.4.25-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #93267
Email or phone of affected tester (no customers): ldaksjflkajdsflkjew@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: macOS chrome
App Component: Other

Action Performed:

1. Open ND
2. Login with new account without + iteration
3. In onboarding steps, choose "Manage my team's expenses" > "1-4 employees" > "QuickBooks Online" > Click "Continue"
4. Click on dropdown icon on admin room header

Expected Result:

Admin room details should open

Actual Result:

Not found page opened

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7195357_1782825895357.Screen_Recording_2026-06-30_at_4.23.05_in_the_afternoon.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7195357

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022078173635597120579
• Upwork Job ID: 2078173635597120579
• Last Price Increase: 2026-07-17

Issue Owner

Current Issue Owner: @lorretheboy

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/e486ed5dc8ab8f993918c9f5750a8f593033bf3d3fd3898e6b703d9714cd58eb

[MelvinBot]

Issue Analysis

Root cause: The report details page and the chat screen use different not-found guards, and only the details guard rejects the admin room. When you tap the #admins header dropdown, it opens report details via withReportOrNotFound, which shows the "Not found" page whenever canAccessReport returns false. canAccessReport returns false if the room carries a (transient/stale) errorFields.notFound, or if #admins is treated as a default room the brand-new account can't yet access. The chat itself opens fine because ReportNotFoundGuard (used by ReportScreen) never calls canAccessReport — this is the asymmetry. This matches the diagnosis in the closely-related, now-closed #90898.

Proposal

What is the root cause of that problem?

Right after "Manage my team's expenses" onboarding, the account lands in the optimistically-created #admins room. Tapping the header dropdown navigates to report details, wrapped by withReportOrNotFound. That HOC computes shouldShowNotFoundPage = !isReportLoaded || !canAccessReport(report, betas, isReportArchived). Even though the room object is fully loaded, canAccessReport returns false because the freshly-created onboarding room briefly has errorFields.notFound set (this truthy value originates from the server response and is never cleared in time; the client only ever reads or clears it), and/or #admins is a default room the new account can't yet see. ReportScreen renders the same report without issue because its guard (ReportNotFoundGuard) checks only for an invalid path or a truly-absent report — it never consults canAccessReport or errorFields.notFound. The QuickBooks Online integration selection appears to matter only because the extra workspace/connection work lengthens the window before the room is fully persisted server-side, widening this transient race.

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

Bring the report-details not-found guard in line with the chat guard so the two can't disagree for a report the user is actively viewing:

• In withReportOrNotFound, do not treat a loaded report as "not found" purely because of a transient errorFields.notFound while the report is still being fetched/persisted (e.g. gate on the same loading/reportExists conditions ReportNotFoundGuard uses, rather than a raw canAccessReport check that fails on a stale flag).
• And/or ensure the stale errorFields.notFound on the optimistically-created onboarding #admins room is cleared once the room is confirmed (the client already clears notFound to null in OpenReport success data — the gap is that details can render before that clear lands).

What alternative solutions did you explore? (Optional)

Clearing/ignoring errorFields.notFound specifically for onboarding-created rooms; or confirming (via backend/log investigation) whether the server should stop returning errorFields.notFound for a room it just created during onboarding.

Investigation details & evidence

Navigation path: header dropdown press → HeaderView.tsx:359-362 → navigateToDetailsPage (ReportUtils.ts:6364-6377) → DynamicReportDetailsPage, wrapped by withReportOrNotFound().

The gate: withReportOrNotFound.tsx:116 — shouldShowNotFoundPage = !isReportLoaded || !canAccessReport(...), renders NotFoundPage when true.

canAccessReport: ReportUtils.ts:9321-9332 returns false on report.errorFields.notFound or default-room-without-beta.

Chat's different guard: ReportNotFoundGuard.tsx:52-73 gates only on invalid path / report-absent-after-load. Never calls canAccessReport.

Optimistic creation: the #admins room is built fully-formed (real reportID, policyID, chatType: POLICY_ADMINS) in buildOptimisticWorkspaceChats and written in Policy.ts; no client code ever sets errorFields.notFound to a truthy value — it is only read or cleared to null (e.g. OpenReport success data). So the truthy value is server-originated and transient.

Confidence: Medium-High. The client-side guard asymmetry is confirmed with file:line evidence. The exact server-side trigger and why QuickBooks Online specifically widens the race window would benefit from production log confirmation for a repro requestID (checking whether the OpenReport/reconnect response for the admins reportID returns errorFields.notFound, and its timing relative to workspace creation).

Note on scope: the App-side guard fix above is fully actionable within Expensify/App. If the team prefers to stop the transient errorFields.notFound at the source, that part involves the backend and would need an internal engineer to confirm.

Related issues

• [$250] Onboarding - Hmm it's not here page displayed when tap on report header for any task #90898 (CLOSED) — same "Hmm… it's not here" symptom on onboarding report headers; diagnosed the same errorFields.notFound / guard-asymmetry root cause.
• [Due for payment 2026-07-03] [$250] Onboarding - Not here page appears briefly after completing onboarding #91437 (CLOSED) — "Not here" page appears briefly after completing onboarding.

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/94977) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @marufsharifi (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022078173635597120579