[Splits in NewDot] Error when saving split when there is only one split after readding unreported split

[jponikarchuk]

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.2.27-0
Reproducible in staging?: Yes
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: #63738
Email or phone of affected tester (no customers): applausetester+jdoisjs1@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Log in with Expensifail account.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense in workspace chat.
4. Open expense report.
5. Click More > Split.
6. Click Save.
7. Open any split.
8. Click Report.
9. Click Remove from report.
10. Click More > Add expense > Add unreported expense.
11. Add back the unreported expense from Step 9.
12. Open the newly added split (from Step 11).
13. Click More > Edit splits.
14. Open the other (not highlighted) split.
15. Click Remove split.
16. Click Save.

Expected Result:

App should not allow to save when there is only one split (minimum split is two).

Actual Result:

App allows to save when there is only one split after readding the unreported split.
Error shows up after saving the resulting split.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

11.mp4

View all open jobs on GitHub

[melvin-bot]

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

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

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

[ZhenjaHorbach]

This feature is in beta
So I suppose we can remove the deploy blocker label here