Skip to content

Conversation

@ZhenjaHorbach
Copy link
Contributor

@ZhenjaHorbach ZhenjaHorbach commented Oct 8, 2025

Split expense flow (Phase 2 - Reverting existing split expenses)

Explanation of Change

Fixed Issues

$ #61029

PROPOSAL: NA

Tests

  1. Enable newDotRevertSplits beta
  2. Navigate to an eligible expense in your reports or expenses list.
  3. Open the More menu.
  4. Click the Split button.
  5. Save the splits.
  6. Open the created split transaction.
  7. Click the Edit splits button in More menu or click the amount to open the split screen.
  8. Remove the splits to leave one.
  9. Verify that the split has been reverted correctly and the current split works as a default expense
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  1. Enable newDotRevertSplits beta
  2. Navigate to an eligible expense in your reports or expenses list.
  3. Open the More menu.
  4. Click the Split button.
  5. Save the splits.
  6. Open the created split transaction.
  7. Click the Edit splits button in More menu or click the amount to open the split screen.
  8. Remove the splits to leave one.
  9. Verify that the split has been reverted correctly and the current split works as a default expense
  • 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
    • MacOS: Desktop
  • 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-09-29.16.52.42.mov
Android: mWeb Chrome
2025-09-29.16.52.42.mov
iOS: Native
2025-09-29.16.52.42.mov
iOS: mWeb Safari
2025-09-29.16.52.42.mov
MacOS: Chrome / Safari
2025-09-29.16.52.42.mov
MacOS: Desktop
2025-09-29.16.52.42.mov

@ZhenjaHorbach ZhenjaHorbach marked this pull request as ready for review October 8, 2025 12:06
@ZhenjaHorbach ZhenjaHorbach requested a review from a team as a code owner October 8, 2025 12:06
@melvin-bot melvin-bot bot requested a review from eh2077 October 8, 2025 12:06
@melvin-bot
Copy link

melvin-bot bot commented Oct 8, 2025

@eh2077 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]

@melvin-bot melvin-bot bot removed the request for review from a team October 8, 2025 12:06
@lakchote lakchote self-requested a review October 8, 2025 12:08
@lakchote
Copy link
Contributor

lakchote commented Oct 8, 2025

@eh2077 this is a very high priority one, as we want the splits feature to be live next week.

@eh2077
Copy link
Contributor

eh2077 commented Oct 8, 2025

Got it, reviewing it!

@codecov
Copy link

codecov bot commented Oct 8, 2025

Codecov Report

❌ Patch coverage is 33.10811% with 99 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/hooks/useDeleteTransactions.ts 15.62% 54 Missing ⚠️
src/libs/actions/IOU.ts 70.00% 12 Missing ⚠️
src/pages/iou/SplitExpensePage.tsx 0.00% 7 Missing ⚠️
src/components/MoneyReportHeader.tsx 0.00% 6 Missing ⚠️
src/components/MoneyRequestHeader.tsx 0.00% 6 Missing ⚠️
...c/components/ReportActionItem/MoneyRequestView.tsx 0.00% 4 Missing ⚠️
src/hooks/useSelectedTransactionsActions.ts 0.00% 4 Missing ⚠️
...ort/ContextMenu/PopoverReportActionContextMenu.tsx 50.00% 4 Missing ⚠️
src/pages/ReportDetailsPage.tsx 60.00% 2 Missing ⚠️
Files with missing lines Coverage Δ
src/libs/API/types.ts 100.00% <ø> (ø)
src/libs/TransactionUtils/index.ts 68.43% <100.00%> (ø)
src/pages/ReportDetailsPage.tsx 58.82% <60.00%> (+0.36%) ⬆️
...c/components/ReportActionItem/MoneyRequestView.tsx 0.28% <0.00%> (-0.01%) ⬇️
src/hooks/useSelectedTransactionsActions.ts 3.22% <0.00%> (+0.42%) ⬆️
...ort/ContextMenu/PopoverReportActionContextMenu.tsx 40.10% <50.00%> (+1.27%) ⬆️
src/components/MoneyReportHeader.tsx 0.18% <0.00%> (-0.01%) ⬇️
src/components/MoneyRequestHeader.tsx 0.61% <0.00%> (-0.02%) ⬇️
src/pages/iou/SplitExpensePage.tsx 0.00% <0.00%> (ø)
src/libs/actions/IOU.ts 63.67% <70.00%> (+<0.01%) ⬆️
... and 1 more

... and 14 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@eh2077
Copy link
Contributor

eh2077 commented Oct 8, 2025

Is BE ready? I'm using staging server and the RevertSplitTransaction command returned error

Screen.Recording.2025-10-08.at.11.21.31.PM.mov

@eh2077
Copy link
Contributor

eh2077 commented Oct 8, 2025

Bug: Get one split after deleting the other split

  1. create an expense
  2. split expense
  3. open a split expense
  4. click secondary delete button to delete a split expense
  5. the remain split expense is not reverted
Screen.Recording.2025-10-08.at.11.59.10.PM.mov

@eh2077
Copy link
Contributor

eh2077 commented Oct 8, 2025

Bug: Offline - distance splits - system message contains pending keyword after reverting

Screen.Recording.2025-10-09.at.12.08.04.AM.mov

@ZhenjaHorbach
Copy link
Contributor Author

Is BE ready? I'm using staging server and the RevertSplitTransaction command returned error

Screen.Recording.2025-10-08.at.11.21.31.PM.mov

Strange
Everything works for me
But actually staging server is enabled for me
Maybe that's the reason

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Oct 8, 2025

Bug: Get one split after deleting the other split

  1. create an expense
  2. split expense
  3. open a split expense
  4. click secondary delete button to delete a split expense
  5. the remain split expense is not reverted

Screen.Recording.2025-10-08.at.11.59.10.PM.mov

Oh
Yeah
I suppose we need to call the save split function here also

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Oct 8, 2025

Bug: Offline - distance splits - system message contains pending keyword after reverting

Screen.Recording.2025-10-09.at.12.08.04.AM.mov

Fixed !

@eh2077
Copy link
Contributor

eh2077 commented Oct 8, 2025

Bug: comments of the original expense isn't shown under the split table (they're in the same report ID)

  1. create an expense
  2. add a comment in the expense thread
  3. split expense
  4. the comment is not shown under the split table but the parent report preview action indicates the comment exists

After reverting splits, do we need to show comments of the original expense?

Screen.Recording.2025-10-09.at.12.18.12.AM.mov

Copy link
Contributor

@eh2077 eh2077 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good so far, just a comment about TS types.

@eh2077
Copy link
Contributor

eh2077 commented Oct 8, 2025

Is BE ready? I'm using staging server and the RevertSplitTransaction command returned error
Screen.Recording.2025-10-08.at.11.21.31.PM.mov

Strange Everything works for me But actually staging server is enabled for me Maybe that's the reason

Hmm, so that means my account ericwdev001+63738c@gmail.com needs to be whitelist in BE, right? cc @lakchote

@ZhenjaHorbach
Copy link
Contributor Author

Bug: comments of the original expense isn't shown under the split table (they're in the same report ID)

  1. create an expense
  2. add a comment in the expense thread
  3. split expense
  4. the comment is not shown under the split table but the parent report preview action indicates the comment exists

After reverting splits, do we need to show comments of the original expense?

Screen.Recording.2025-10-09.at.12.18.12.AM.mov

Actually good question
I suppose it's because we still have the invisible original transaction, which we don't show in the report (but still have report actions from this transaction)

@ZhenjaHorbach
Copy link
Contributor Author

Is BE ready? I'm using staging server and the RevertSplitTransaction command returned error
Screen.Recording.2025-10-08.at.11.21.31.PM.mov

Strange Everything works for me But actually staging server is enabled for me Maybe that's the reason

Hmm, so that means my account ericwdev001+63738c@gmail.com needs to be whitelist in BE, right? cc @lakchote

I don't think so
I didn't give my email to anyone

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Oct 9, 2025

Is BE ready? I'm using staging server and the RevertSplitTransaction command returned error

Screen.Recording.2025-10-08.at.11.21.31.PM.mov

About this
Sorry for confusing
If we don't pass a comment or category (which are optional), BE returns an error
But this will be fixed soon from BE side

@lakchote
Copy link
Contributor

lakchote commented Oct 22, 2025

@ZhenjaHorbach there are conflicts and lint failing, let's push this one to the finish line!

lakchote
lakchote previously approved these changes Oct 23, 2025
@lakchote lakchote merged commit 8c11c1e into Expensify:main Oct 23, 2025
24 of 25 checks passed
@lakchote
Copy link
Contributor

The eslint check failing is unrelated to this PR, see https://expensify.slack.com/archives/C01GTK53T8Q/p1761207966046699

@melvin-bot melvin-bot bot added the Emergency label Oct 23, 2025
@melvin-bot
Copy link

melvin-bot bot commented Oct 23, 2025

@lakchote looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

@lakchote
Copy link
Contributor

Not an emergency, see #72086 (comment)

@izarutskaya
Copy link

Hi @ZhenjaHorbach

Enable newDotRevertSplits beta

Can we check testing this PR with Expensifail accounts or we need some specific settings?

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/lakchote in version: 9.2.37-1 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Oct 23, 2025

Hi @ZhenjaHorbach

Enable newDotRevertSplits beta

Can we check testing this PR with Expensifail accounts or we need some specific settings?

As far as I know, Expensifail accounts always have all betas enabled
If yes
Then you can test on Expensifail accounts without specific settings!

Comment on lines -808 to +816
} else {
deleteMoneyRequest(
iouTransactionID,
requestParentReportAction,
duplicateTransactions,
duplicateTransactionViolations,
iouReport,
chatIOUReport,
isChatIOUReportArchived,
isSingleTransactionView,
);
} else if (iouTransactionID) {
deleteTransactions([iouTransactionID], duplicateTransactions, duplicateTransactionViolations, currentSearchHash, isSingleTransactionView);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ZhenjaHorbach Could these changes be causing #73330 ?

I'm reverting these here https://github.com/Expensify/App/pull/73379/files and it seems to fix the issue

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Honestly, I never would have thought it was related to this PR
Because the issue is the broken navigation, which we didn't change
But I will try to fix !

@izarutskaya
Copy link

@ZhenjaHorbach PR is failing only on Desktop, iOS with #73383

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Oct 24, 2025

@ZhenjaHorbach PR is failing only on Desktop, iOS with #73383

Thanks for testing!

Looks like a BE issue
But I will try to find the root cause

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/blimpich in version: 9.2.37-8 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants