[HOLD for payment 2024-12-03] [Search v1.2] - Unable to pay held expense in Search

[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.60-0
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers): applausetester+kh011101@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

Precondition:

• User has paid expense in Search before.

1. Go to staging.new.expensify.com
2. [User A] Submit an expense to User B.
3. [User B] Go to transaction thread > Click report header.
4. [User B] Click Hold expense, enter reason and save it.
5. [User B] Go to Search.
6. [User B] Click Pay button for the held expense.

Expected Result:

Confirmation modal will show when paying held expense in Search.

Actual Result:

Confirmation modal does not show when paying held expense in Search. The pay button shows loading and then reverts to initial state.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6661871_1731361819203.20241112_054704.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @OfstadC

[melvin-bot]

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

[melvin-bot]

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

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

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

[iwiznia]

Feature was added in this PR #51445

@IuliiaHerets was this issue open while testing that PR? If so, you should've noted that, so the assigned person does not need to go find it.

ccing @luacmartins because it's your PR, but looking into it now.