Skip to content

It's not here page opens instead of fraud alert report #82242

Closed

Description

@nlemma

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.3.17-3
Reproducible in staging?: Yes
Reproducible in production?: Unable to validate in Prod - Provide reasoning.
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #81058
Email or phone of affected tester (no customers): -
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: MacOS Monterey 12.7.4 / Chrome
App Component: Other

Action Performed:

Prerequisites:
Logged in user with an Expensify Card

STR:

  1. Open DevTools console > Apply mock data and run:
Onyx.merge('cardList', { '12345': { cardID: 12345, accountID: 18439984, bank: 'Expensify Card', availableSpend: 5000, domainName: 'expensify-policy123.exfy', fraud: 'individual', fundID: '123456', lastFourPAN: '1234', state: 3, isVirtual: false, nameValuePairs: { isVirtual: false }, message: { possibleFraud: { state: 1, date: '2025-01-29',triggerAmount: 50000, triggerMerchant: 'Gucci', triggerCurrency: 'GBP', fraudAlertReportID: 999888777, fraudAlertReportActionID: 111222333 } } } });

Onyx.merge('reportActions_999888777', { '111222333': { reportActionID: '111222333', actionName: 'ACTIONABLECARDFAUDALERT', created: '2025-01-29 10:00:00.000', actorAccountID: 1, originalMessage: { cardID: 12345, maskedCardNumber: 'XXXXXXXXXXXX1234', triggerAmount: 50000, triggerMerchant: 'Gucci', currency: 'USD' } } });
  1. Navigate to Home page
  2. Click red "Review" button on a widget in the Time Sensitive section

Expected Result:

User should navigated to the fraud alert report

Actual Result:

User is navigated to It's not here page

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7074779_1770822361942.16.36.48.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 12, 2026
  2. melvin-bot commented on Feb 12, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #81058

  3. melvin-bot commented on Feb 12, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  4. melvin-bot commented on Feb 12, 2026

    @melvin-bot

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

  5. github-actions commented on Feb 12, 2026

    @github-actions
    Contributor

    👋 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.
  6. OSBotify commented on Feb 12, 2026

    @OSBotify
    Contributor

    🔍 Investigation Summary

    Classification: Frontend bug
    Causing PR: #81058 - "[Home Page] [Release 3] Add card fraud alert" by @mountiny (High confidence)
    Related Issues: N/A

    Recommendation: REVERT

    The PR introduces a new fraud alert widget that navigates to a report without properly opening/fetching it first. This causes the "Its not here" page to appear when users try to review fraud alerts.

    Labels: Keeping DeployBlockerCash - this is a frontend bug that needs to be reverted or fixed before the App deploy can proceed. The issue is reproducible in staging and blocks the deployment.

    📋 Detailed Analysis

    Evidence

    PR #81058 added the ReviewCardFraud.tsx component which is displayed when a card has potential fraud (card.fraud === "domain" or card.fraud === "individual"). The component renders a widget in the Time Sensitive section of the Home page.

    When users click the "Review" button, the component calls:

    Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(String(fraudAlertReportID)));

    This directly navigates to a report without first fetching/opening it.

    Verification

    The bug report provides exact reproduction steps using the mock data from the PR description:

    1. User merges card data with fraudAlertReportID: 999888777
    2. User clicks "Review" button on the fraud widget
    3. App navigates to report 999888777
    4. Report doesnt exist in local Onyx store → "Its not here" page appears

    The files modified by PR #81058 that relate to this bug:

    • src/pages/home/TimeSensitiveSection/items/ReviewCardFraud.tsx (NEW - contains the buggy navigation code)
    • src/pages/home/TimeSensitiveSection/index.tsx (renders the new widget)
    • src/types/onyx/Card.ts (adds fraudAlertReportID field)

    Root Cause

    The ReviewCardFraud component at line 43 navigates to a report without opening it first:

    const handleReviewPress = () => {
        // Navigate to the report containing the fraud alert action
        Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(String(fraudAlertReportID)));
    };

    The proper pattern used throughout the codebase (e.g., in TransactionDuplicate/Review.tsx, SearchMoneyRequestReportPage.tsx) is to call openReport() from @libs/actions/Report before or as part of navigation:

    import {openReport} from @libs/actions/Report;
    
    // Then before/during navigation:
    openReport(reportID, introSelected, reportActionID);

    The openReport() function fetches the report from the backend if it doesnt exist locally, preventing the "Its not here" page from appearing.

    Why REVERT is recommended

    1. The fix requires adding the openReport() call before navigation
    2. This is a clear regression introduced by PR [Home Page] [Release 3] Add card fraud alert #81058
    3. The feature is new (Release 3) and reverting wont break existing functionality
    4. Issue is reproducible in staging, confirming its in the current deploy
    5. Clean revert path - no dependent PRs have been merged since
  7. ZhenjaHorbach commented on Feb 12, 2026

    @ZhenjaHorbach
    Contributor

    I suppose it's not a regression
    Since in the mock onyx example we just used the minimum information to confirm that navigation is working

    CC: @mountiny

  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Feb 12, 2026
  9. mountiny commented on Feb 12, 2026

    @mountiny
    Contributor

    Not a blocker, that is just from the mocks, I will need to test once someone hits the fraud alert

  10. JmillsExpensify commented on Feb 12, 2026

    @JmillsExpensify
    Contributor

    Agree it's not a blocker

  11. mountiny commented on Feb 12, 2026

    @mountiny
    Contributor

    we did CP an update though waiting for more users who hit this

  12. mountiny commented on Feb 20, 2026

    @mountiny
    Contributor

    All good now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions