Add date range limit for splits

[ZhenjaHorbach]

Explanation of Change

Fixed Issues

$ #78207
PROPOSAL:

Tests

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

1. Open 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 a day range of more than 50 days
9. Verify that the date range limit error is displayed.

• Verify that no errors appear in the JS console

Offline tests

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

1. Open 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 a day range of more than 50 days
9. Verify that the date range limit error is displayed

QA Steps

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

1. Open 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 a day range of more than 50 days
9. Verify that the date range limit error is displayed

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

2025-12-26.12.53.52.mov

Android: mWeb Chrome

iOS: Native

2025-12-26.12.53.52.mov

iOS: mWeb Safari

MacOS: Chrome / Safari

[melvin-bot]

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

1. Look at the code and make sure there are no malicious changes.
2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

[codecov]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/CONST/index.ts	83.47% <ø> (ø)
src/pages/iou/SplitExpenseCreateDateRagePage.tsx	0.00% <0.00%> (ø)
... and 5 files with indirect coverage changes

[melvin-bot]

@suneox Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[ZhenjaHorbach]

@parasharrajat is a reviewer here

But I think it's better to wait for the BZ team, when they return after the holidays, to decide whether this fix is right for them

[parasharrajat]

IMO, 50 is a magic number. This should be more systematic like 2 months/60 days or 30 days.

[ZhenjaHorbach]

I already tested 60
And that's still a lot for iOS

[parasharrajat]

Yes, I noticed that even with fewer split,s like 13, this page is slow. I think we should optimize this page. 60 or 100 should be no problem as we are just creating data and rendering it list. Something on this page is very expensive or may be poorly implemented.

[ZhenjaHorbach]

When I tested 100 and 200 splits
Splits were easy to create
But when I tried to save and create split transactions
The app crashed

[parasharrajat]

Yes especially when I save and the page closes, it was very slow.

[ZhenjaHorbach]

But on the other hand,
On the web,
700 transactions are created just fine
So everything works as expected.

But probably, iOS has some limitations with Onyx

But in any case, it's better to wait to see what the BZ team says
Since, in my opinion, even 30 or 45 splits would be enough
Since I doubt anyone will really need that many splits

[parasharrajat]

Sure, sounds good.