You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-11-20] Split - "Please enter a valid amount before continuing." error message persist #74975
Version Number: 9.2.55-3 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail:#74407 Email or phone of affected tester (no customers):gocemate+b2155178@gmail.com Issue reported by: Applause - Internal Team
Action Performed:
Create an expense for $10
Select 'Split' from the 'More' menu for the expense
Tap 'Add split' to create a 3rd split
Tap 'Add split' to create a 4th split
Click Save
Verify error message is displayed
Tap 'Make splits even'
Verify the amounts of the split expenses are all $2.50
Expected Result:
The error message should disappear
Actual Result:
"Please enter a valid amount before continuing." error message persist even split amounts are equal
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug7001908_1762967611181.Recording__6762.mp4
👋 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:
Identify the pull request that introduced this issue and revert it.
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
changed the title [-]Split - "Please enter a valid amount before continuing." error message persist[/-][+][Due for payment 2025-11-20] Split - "Please enter a valid amount before continuing." error message persist[/+]on Nov 13, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.57-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@lakchote@RachCHopkins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Nov 12, 2025
Triggered auto assignment to @RachCHopkins (
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 commentedon Nov 12, 2025
Triggered auto assignment to @inimaga (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Nov 12, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 12, 2025
👋 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:
samranahm commentedon Nov 12, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
Split - "Please enter a valid amount before continuing." error message persist
What is the root cause of that problem?
The error clearing useEffect in
SplitExpensePageonly monitored two dependenciesWhen "Make splits even" redistributes amounts evenly across existing splits, neither the sum nor the count changes.
App/src/pages/iou/SplitExpensePage.tsx
Lines 109 to 111 in 112cc07
What changes do you think we should make in order to solve the problem?
We should include
splitExpensesin deps arrayWhat alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
1 remaining item
lakchote commentedon Nov 13, 2025
@samranahm I've used your proposal here. I've raised a PR to save time and solve this with urgency.
samranahm commentedon Nov 13, 2025
@lakchote All good, glad my proposal helped fix the issue!
lakchote commentedon Nov 13, 2025
Asked for QA retest here: https://expensify.slack.com/archives/C9YU7BX5M/p1763038606182729
m-natarajan commentedon Nov 13, 2025
Not reproduce, MacOS Monterey / Chrome, Web v9.2.57-3
Screen.Recording.2025-11-13.at.15.08.38.mp4
lakchote commentedon Nov 13, 2025
Not reproducible, closing the issue.
[-]Split - "Please enter a valid amount before continuing." error message persist[/-][+][Due for payment 2025-11-20] Split - "Please enter a valid amount before continuing." error message persist[/+]melvin-bot commentedon Nov 13, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Nov 13, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.57-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
useEffectto reset splits error #75033If no regressions arise, payment will be issued on 2025-11-20. 🎊
melvin-bot commentedon Nov 13, 2025
@lakchote @RachCHopkins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]