[$250] Track Expense - Not here page opens after clicking on the report header.

[mitarachim]

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.34-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: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1376/folder/13176877/41237357/962799891
Email or phone of affected tester (no customers): joelarmandotester+473@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 11 / Chrome, iOS 26 / iPhone 12, Android 15 / Samsung A16)
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Log in with the new Gmail account in incognito mode.
3. Skip work email
4. Complete the incorporation process using the option “Track and Budget Expenses”
5. Enter a first name (only) and click on the Continue button, and create a Workspace.
6. Skip invite members
7. Skip Test Drive
8. Click on "+" Fab Button and create a manual Expense with $1.
9. Click on the "Next" button, click on workspace under the "To" section, and choose yourself DM.
10. Click on "Submit it to someone" and select the workspace created.
11. Click on the Report, and click on the Header of the report.

Expected Result: You should show details in the RHP about the report.

Actual Result:

The error is displayed, saying that the page is not there.

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

Bug6980093_1760991940838.Issue.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021980782248076297058
• Upwork Job ID: 1980782248076297058
• Last Price Increase: 2025-10-21

Issue Owner

Current Issue Owner: @shubham1206agra

[melvin-bot]

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

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

[Christinadobrzyn]

I updated the OP steps a tad bit and can reproduce this. Adding external to start there.

[melvin-bot]

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

[cosmicvulpes]

Proposal

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

When a user creates or opens a new expense report and then taps the report header, the app navigates to /r/<reportID>/details but shows a “Hmm… it’s not here” / 404 page instead of the Expense Report Details.

What is the root cause of that problem?

Immediately after a report is optimistically created it contains errorFields.notFound (a temporary placeholder). canAccessReport() blocks navigation whenever this field is present, even though the report is still pending creation (pendingFields.createChat = 'add'). As a result, the Details screen decides the report is inaccessible and displays the Not Found view.

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

In canAccessReport() ( src/libs/ReportUtils.ts ):

• If errorFields.notFound exists but the report is still pending creation (pendingFields.createChat === 'add'), treat it as accessible instead of blocked.
• All other cases remain unchanged, so genuine 404s are still blocked.

function canAccessReport(report: OnyxEntry<Report>, betas: OnyxEntry<Beta[]>, isReportArchived = false): boolean {
    // We hide default rooms (it's basically just domain rooms now) from people who aren't on the defaultRooms beta.
    if (isDefaultRoom(report) && !canSeeDefaultRoom(report, betas, isReportArchived)) {
        return false;
    }

    // When a report is created optimistically it may briefly contain `errorFields.notFound` until the server confirms its
    // creation. If we also see that it is still pending creation, treat it as accessible so navigation (e.g., to the
    // Details page) succeeds immediately after creation.
    if (report?.errorFields?.notFound) {
        const isPendingCreation = report?.pendingFields?.createChat === CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD;
        if (!isPendingCreation) {
            return false;
        }
    }

    return true;
}

This single-line guard allows optimistic reports to open their Details page immediately after creation without waiting for the server.

What alternative solutions did you explore? (Optional)

• Server-side change – stop broadcasting errorFields.notFound for reports that are still processing.
• Strip the flag at merge-time – intercept Onyx updates and omit errorFields.notFound when pendingFields.createChat==='add'.
• Client retry / polling – if Details loads a 404, auto-retry after a short delay. Feels flaky and could mask real access errors.

Our chosen single-check in canAccessReport() is simpler, safer, and fully contained on the client.

[huult]

This is a backend issue because when we submit it to someone, the API call AddTrackedExpenseToPolicy returns an error

Screen.Recording.2025-10-22.at.13.04.17.mov