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 2026-05-26] [$500] Expense-After deleting per diem split expense,remaining 2 split expense shows unexpected error #79067
Version Number: V9.2.95-3 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack:#78637 Email or phone of affected tester (no customers): Redminote 10S Android 13 Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Redminote 10S Android 13 App Component: Workspace Settings
Action Performed:
Pre-condition: Enable per diem and import per diem rates
Launch app
Open workspace chat
Create a per diem expense
Tap more - split the expense
Add a split - make split even - save
Long press a split expense
From top dropdown, delete the split expense
Expected Result:
The user will be navigated to the individual split in the split table and see the option to Remove split. After they remove the split they can edit other splits to allow saving.
Actual Result:
After deleting per diem split expense, remaining 2 split expense shows unexpected error.
Please re-state the problem that we are trying to solve in this issue.
After deleting a per diem split expense, the remaining split expenses show an unexpected error instead of functioning normally.
What is the root cause of that problem?
When per diem expenses are split, the split expense transactions are created without the customUnit data and pendingFields.subRates that identify them as per diem transactions. As a result, the system fails to recognize these split transactions as valid per diem expenses, leading to validation errors during operations such as deletion.
What changes do you think we should make in order to solve the problem?
Update the split transaction parameters to correctly preserve per diem metadata.
This ensures that split transactions retain the necessary per diem identifiers when isPerDiem is true.
What alternative solutions did you explore? (Optional)
Modifying initSplitExpense to include per diem data at creation time
This would prevent the issue for newly created splits but would not resolve the problem for existing split expenses.
Adding per diem validation in the UI layer
This would act as a band-aid solution and mask the underlying data inconsistency rather than fixing it at the transaction level.
Please re-state the problem that we are trying to solve in this issue
After deleting a per diem split expense, the remaining split expenses show an unexpected error instead of functioning normally.
What is the root cause of that problem?
When per diem expenses are split, the split expense transactions are created without inheriting the customUnit data and pendingFields.subRates from the original per diem transaction that identify them as per diem transactions.
What changes do you think we should make in order to solve the problem?
Update the split transaction parameters in the updateSplitTransactions function to inherit per diem metadata from the original transaction.
changed the title [-]Expense-After deleting per diem split expense,remaining 2 split expense shows unexpected error[/-][+][$250] Expense-After deleting per diem split expense,remaining 2 split expense shows unexpected error[/+]on Jan 14, 2026
changed the title [-][Due for payment 2026-05-26] [$250] Expense-After deleting per diem split expense,remaining 2 split expense shows unexpected error[/-][+][Due for payment 2026-05-26] [$500] Expense-After deleting per diem split expense,remaining 2 split expense shows unexpected error[/+]on Jun 11, 2026
@marufsharifi can you please accept the job below? Please reply here and tag me once you have.
If you're not sent an offer in Upwork when you're assigned to an issue, please tag me. If an Upwork job exists, please submit a proposal. Even if an increase is being discussed always except offers cuz bonuses are easy to add to bump up the price, if needed. https://www.upwork.com/jobs/~022065180081308763635
Activity
melvin-bot commentedon Jan 8, 2026
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.twinkle-react commentedon Jan 8, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
After deleting a per diem split expense, the remaining split expenses show an unexpected error instead of functioning normally.
What is the root cause of that problem?
When per diem expenses are split, the split expense transactions are created without the
customUnitdata andpendingFields.subRatesthat identify them as per diem transactions. As a result, the system fails to recognize these split transactions as valid per diem expenses, leading to validation errors during operations such as deletion.What changes do you think we should make in order to solve the problem?
Update the split transaction parameters to correctly preserve per diem metadata.
File:
src/libs/actions/IOU/index.tsFunction:
updateSplitTransactionsThis ensures that split transactions retain the necessary per diem identifiers when
isPerDiemis true.What alternative solutions did you explore? (Optional)
Modifying
initSplitExpenseto include per diem data at creation timeThis would prevent the issue for newly created splits but would not resolve the problem for existing split expenses.
Adding per diem validation in the UI layer
This would act as a band-aid solution and mask the underlying data inconsistency rather than fixing it at the transaction level.
yatin-italy commentedon Jan 8, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue
After deleting a per diem split expense, the remaining split expenses show an unexpected error instead of functioning normally.
What is the root cause of that problem?
When per diem expenses are split, the split expense transactions are created without inheriting the
customUnitdata andpendingFields.subRatesfrom the original per diem transaction that identify them as per diem transactions.What changes do you think we should make in order to solve the problem?
Update the split transaction parameters in the
updateSplitTransactionsfunction to inherit per diem metadata from the original transaction.File:
src/libs/actions/IOU/index.tsFunction:
updateSplitTransactionsThis ensures that per diem split transactions inherit the necessary metadata from their parent transaction.
What alternative solutions did you explore? (Optional)
pendingFieldsstructure – works but is less maintainable if the structure changes.melvin-bot commentedon Jan 13, 2026
@johncschuster Huh... This is 4 days overdue. Who can take care of this?
[-]Expense-After deleting per diem split expense,remaining 2 split expense shows unexpected error[/-][+][$250] Expense-After deleting per diem split expense,remaining 2 split expense shows unexpected error[/+]melvin-bot commentedon Jan 14, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022011239026036015929
melvin-bot commentedon Jan 14, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav (
External)100 remaining items
melvin-bot commentedon Jun 4, 2026
@yuwenmemon Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Jun 8, 2026
@yuwenmemon Still overdue 6 days?! Let's take care of this!
mallenexpensify commentedon Jun 9, 2026
@yuwenmemon 👀 above on potential price increase. thx
yuwenmemon commentedon Jun 10, 2026
Yeah, that's fine by me.
[-][Due for payment 2026-05-26] [$250] Expense-After deleting per diem split expense,remaining 2 split expense shows unexpected error[/-][+][Due for payment 2026-05-26] [$500] Expense-After deleting per diem split expense,remaining 2 split expense shows unexpected error[/+]melvin-bot commentedon Jun 11, 2026
Upwork job price has been updated to $500
mallenexpensify commentedon Jun 11, 2026
@marufsharifi can you please accept the job below? Please reply here and tag me once you have.
If you're not sent an offer in Upwork when you're assigned to an issue, please tag me. If an Upwork job exists, please submit a proposal. Even if an increase is being discussed always except offers cuz bonuses are easy to add to bump up the price, if needed.
https://www.upwork.com/jobs/~022065180081308763635
marufsharifi commentedon Jun 12, 2026
@mallenexpensify, I've accepted the offer. thanks.
mallenexpensify commentedon Jun 12, 2026
@marufsharifi paid, summary updated above. Thx.
garrettmknight commentedon Jun 16, 2026
$500 approved for @situchan