Expense - Error shows up after editing amount of reverted split to higher amount

[mitarachim]

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.3.34-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #79812
Email or phone of affected tester (no customers): sjodijsiojniodjojsi@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

Precondition :

• Approvals and Payment was enable in workflow

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense (amount 100.00)
4. Open Expense report.
5. Click More > Split > Save.
6. Open any split.
7. Click Report > Create report.
8. On the remaining expense, click Submit and Approve.
9. Close the report.
10. Open the moved expense from Step 7.
11. Click More > Delete > Delete.
12. Open the approved report in Step 8.
13. Click More > Unapprove.
14. Click Amount.
15. Edit to amount higher (110.00) than the original amount in Step 3.

Expected Result:

Amount will be saved because the split is reverted and should not be bound by the original limit.

Actual Result:

Error shows up.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7098228_1773090690767.1.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #79812

[melvin-bot]

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

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