[Due for payment 2026-01-21] iOS - Split - App crashes after split expense by date

[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: v9.2.85-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 BrowserStack: #78027
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 14/ iOS 26.1
App Component: Chat Report View

Action Performed:

Preconditions: User is an Expensifail account and admin have a Workspace

1. Open the Hybrid app
2. Create a manual expense
3. Tap on the expense detail
4. Tap on the More button
5. Tap on the Split
6. Select Date option
7. Tap on Split Dates
8. Select the day from 2024/12/01 to 2026/12/01
9. Tap on the Save button
10. Tap on the Save button

Expected Result:

The app splits the expense

Actual Result:

The app crashes

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

logs.txt

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @johncschuster

[melvin-bot]

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

[parasharrajat]

Interesting edge case, we missed during the initial design. We should restrict the date period. Here, the user is trying to create 600+ splits by selecting a 2-year gap between start and end. Definitely not a real stick. @trjExpensify

[ZhenjaHorbach]

Interesting edge case, we missed during the initial design. We should restrict the date period. Here, the user is trying to create 600+ splits by selecting a 2-year gap between start and end. Definitely not a real stick. @trjExpensify

Yeah
It's an edge case
As far as I remember, I suggested adding a limit
But we decided that it's a very specific case
And as an alternative, I think we can add a limit and show the error that this is a very large range before saving

Because it's very difficult for a mobile app to create and show that many splits 😅