Reports - In reports page, app crashes on searching type: expense status:all

[lanitochka17]

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.1.98-2
Reproducible in staging?: Y
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

Pre-condition: Open account with expenses

1. Go to https://staging.new.expensify.com/home
2. Tap reports
3. Enter: type: expense status:all
4. Tap enter

Expected Result:

In reports page, app must not crash on searching: type: expense status:all

Actual Result:

In reports page, app crashes on searching: type: expense status:all

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
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6924755_1755948213634.Screenrecorder-2025-08-23-16-49-44-213.mp4

View all open jobs on GitHub

[melvin-bot]

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

[github-actions]

👋 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.

[melvin-bot]

Triggered auto assignment to @chuckdries (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

[lanitochka17]

Production:

0-02-01-404e05dc2b4e545385523ca57da5375c9ca4554bbf8508c0cc9f499924f06c28_511fe9d416548c58.1.mp4

[chuckdries]

This appears to be caused by the introduction of getCurrentSearchQueryJSON in getTransactionsSections in src/libs/SearchUIUtils.ts as part of #63623 (see here)

CONST.SEARCH.STATUS.EXPENSE.ALL was changed from 'all' to '' in #64224, but it remains in the search bar and url, so getCurrentSearchQueryJSON, which pulls params straight from the url, picks it up. Then, expenseStatusActionMapping[expenseStatus](report) throws because it tries to access expenseStatusActionMapping['all'], which is undefined because its "all" key is actually ''.

Unfortunately, #63623 looks like a pretty difficult PR to revert. Taking the discussion to slack.

[luacmartins]

Left a comment in Slack. This has been fixed on main by this PR #68480. We can CP that to fix it on staging