[Held requests] Held and unpaid expense disappears when paying only the unheld expense

[lanitochka17]

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.13-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4775912
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. [User A] Submit two expenses to User B
3. [User A] Hold one of the submitted expenses
4. [User B] Go to expense report from User A
5. [User B] Click Pay button
6. [User B] Pay partially the expense (pay the unheld expense)

Expected Result:

For User A and B,

• the paid system message should display "paid elsewhere"
• the unpaid expense will be moved to a new report

Actual Result:

For User A and B,

• the paid system message displays "paid elsewhere"

For User A,

• the unpaid expense disappears.

For User B,

• the unpaid expense becomes negative in another report, and it leads to not here page.
• the unpaid expense disappears after clearing app cache and restarting app.

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

Bug6554706_1722088302329.bandicam_2024-07-27_21-39-39-030.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01d67b0d3a732826c4
• Upwork Job ID: 1821690332875199057
• Last Price Increase: 2024-08-15

Issue Owner

Current Issue Owner: @robertjchen

[melvin-bot]

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

[lanitochka17]

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

[lanitochka17]

@JmillsExpensify 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

[melvin-bot]

@JmillsExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@JmillsExpensify Eep! 4 days overdue now. Issues have feelings too...

[melvin-bot]

@JmillsExpensify Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

[JmillsExpensify]

Going to highlight this one in the project issue.

[JmillsExpensify]

Flagged this in #wave-collect. I'll go ahead and add it to polish for now, though @trjExpensify we can remove depending on how the wave-collect/polish hit list pans out.