[$250] Android - Search - Paid & Approved status is not tappable after opening expense in All status

[IuliiaHerets]

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.0.22-5
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+kh05081@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

PPrecondition:

• Physical (real) device is required to reproduce this issue.

1. Launch New Expensify app.
2. Go to Search.
3. Go to Paid.
4. Note that Paid tab is tappable.
5. Go to All.
6. Open any expense.
7. Tap app back button to return to All.
8. Scroll the status bar.
9. Tap on Paid and Approved status.

Expected Result:

Paid and Approved status should be tappable after opening an expense in All tab.

Actual Result:

Paid and Approved status is no longer tappable after opening an expense in All tab.

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6576818_1724139189477.Screen_Recording_20240820_135555_New_Expensify__1_.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0182def85840821943
• Upwork Job ID: 1825893542863089341
• Last Price Increase: 2024-08-20

Issue Owner

Current Issue Owner: @eVoloshchak

[melvin-bot]

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

[melvin-bot]

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

[IuliiaHerets]

We think that this bug might be related to #wave-collect - Release 1

[flodnv]

Well for me I can't even tap Paid to start with 😕 How about you @joekaufmanexpensify?

This does seem like a blocker.

[flodnv]

Probably caused by #47181 @luacmartins @arosiclair @rayane-djouah ? I'll let you decide whether this should be a blocker.