Spend- Expenses tab opens instead of saved search when saved search is opened via shared link

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.76-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #96466
Email or phone of affected tester (no customers): jsdoijnodsdisojo@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Search

Action Performed:

1. Go to staging.new.expensify.com
2. Go to Spend > Expenses.
3. Apply any filter.
4. Click Save.
5. Enter name and save it.
6. Click 3-dot menu on the saved search > Share.
7. Go to Expenses and click Reset filter.
8. Navigate to the saved search link.

Expected Result:

App will open Saved search tab in LHN when saved search is opened via shared link.

Actual Result:

App opens Expenses tab in LHN when saved search is opened via shared link.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7256848_1789114885799.Recording__2468.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7257055

[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/f4f98880b1d24ee139e4e713a8e1e9fe2cc4618a19bf06414e40bf63c1d0d94c

[melvin-bot]

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

[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]

@JS00001 @aimane-chnaif you have been assigned to this deploy blocker because you reviewed the offending PR: #96466

[melvin-bot]

@bernhardoj you have been assigned to this deploy blocker because you authored the offending PR: #96466

[melvin-bot]

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

[JS00001]

For now, this is expected, @bernhardoj this is the one we wanted to follow up on, so lets keep it open