Workspace chat - Incorrect amount shown in preview card after payment.

[izarutskaya]

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.0.12-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): biruknew45+2d2gg@gmail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Prerequisite: A workspace is created and 2 expenses are submitted in the workspace chat.

1. Go to [staging.new.expensify.com].
2. Navigate to the workspace chat created.
3. Go to the expense details page.
4. Click on the first expense.
5. Click on the header, then select "hold."
6. Write any reason and then click on "hold."
7. Turn off the connection.
8. Click on the "pay with expensify" dropdown and then select "pay elsewhere."
9. Pay the amount.
10. Navigate back to the main workspace chat by clicking on the subtitle link.

Expected Result:

After paying ETB 300, the preview card on the workspace chat page should show that ETB 300 is paid.

Actual Result:

After paying ETB 300, the preview card on the workspace chat page incorrectly shows that ETB 400 is paid.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Bug6553590_1721992163178.1.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[izarutskaya]

We think this issue might be related to the #collect project.

[izarutskaya]

Production

Recording.2653.mp4