Track expense - Total changes to 0.00 when deleting manual request and leaving only trackings

[m-natarajan]

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: 1.4.62-0
Reproducible in staging?: y
Reproducible in production?: no new feature
If this was caught during regression testing, add the test name, ID and link from TestRail: n/a
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat with no request history.
3. Create a track manual expense.
4. Create a manual request (not track expense).
5. Create a second track manual expense.
6. Click on the expense preview.
7. Delete the manual request in Step 4.

Expected Result:

The total amount will update accordingly after deleting the manual request and leaving only track expenses.

Actual Result:

The total amount changes to 0.00 and it only shows the correct total after revisiting the report.

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

Add any screenshot/video evidence

Bug6445101_1712781251437.20240411_042940.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01f9bcc46c20d53fb1
• Upwork Job ID: 1778840188915064832
• Last Price Increase: 2024-04-12

[melvin-bot]

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

[melvin-bot]

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

[m-natarajan]

@garrettmknight FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[m-natarajan]

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

[thienlnam]

Not a blocker, part of new feature of Track. This is also related to #40042 regarding the BE using the total not just reimbursable total

[garrettmknight]

@thienlnam shall we hold on that issue then?

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01f9bcc46c20d53fb1

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @paultsimura (Internal)

[garrettmknight]

Still held on #40042

[garrettmknight]

Off hold - moving to daily to test.

[melvin-bot]

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

[garrettmknight]

@twisterdotcom - I didn't get to retest this and I'm taking off for a few days. Can you test and close if it's fixed?

[twisterdotcom]

Ah god, okay. I'm also off next week but I'll try to squeeze this in.

[twisterdotcom]

I am sorry, I did not get to reset this. Going to add retest label and we'll get QA to do it. We can close if they confirm it's not happening.

[melvin-bot]

@twisterdotcom, @paultsimura, @thienlnam Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@twisterdotcom, @paultsimura, @thienlnam Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[thienlnam]

Pending retest

[mvtglobally]

Issue not reproducible during KI retests. (First week)