[Payment due @rojiphil] Deleted transactions on search V2

[jnowakow]

@luacmartins

Explanation of Change

This PR adds support deleted transactions on search.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/608639
PROPOSAL: N/A

Tests

TC-1: "Unheld the expense" message shown after undeleting a held expense

Issue: #86799
Platforms: Android App, iOS App, Windows Chrome

Steps:

1. Go to a workspace chat.
2. Create an expense.
3. Open the expense and hold it.
4. Delete the held expense.
5. Navigate to Reports > Expenses.
6. Filter by Status = Deleted and Apply.
7. Select the deleted expense via checkbox.
8. Click dropdown > Undelete.
9. Go to Inbox, open self DM, and open the undeleted expense.

Expected: No "Unheld the expense" message is shown (since there's no corresponding "held the expense" message visible).

tc1-unheld.mov

---

TC-2: Tapping expense row does not toggle selection on mobile

Issue: #86780
Platforms: Android App, iOS App

Steps:

1. Go to a workspace chat.
2. Create an expense.
3. Delete the expense.
4. Navigate to Reports > Expenses.
5. Filter by Status = Deleted and Apply.
6. Long-tap on the expense to enter selection mode (Select).
7. Tap on the expense row.

Expected: Tapping the expense row toggles (selects/deselects) the expense.

tc2-tapping-expense.mov

---

TC-3: Deleted expense with negative amount does not show negative in Reports

Issue: #86783
Platforms: MacOS Chrome/Safari

Steps:

1. Go to a workspace chat.
2. Create an expense with a negative amount.
3. Delete the expense.
4. Navigate to Reports > Expenses.
5. Filter by Status = Deleted and Apply.

Expected: The deleted expense displays with its original negative amount.

tc3-negative-amount.mov

---

TC-4: Category column misaligned with table header in deleted expenses view

Issue: #86791
Platforms: Windows Chrome

Steps:

1. Go to a workspace chat.
2. Create two expenses.
3. Delete one of the expenses.
4. Navigate to Reports > Expenses.
5. Filter by Status = Deleted and Apply.

Expected: The Category column data aligns properly with the Category table header.

---

TC-5: Non-functional "View" button shown instead of "Undelete" in grouped search

Issue: #86796
Platforms: Windows Chrome

Steps:

1. Go to a workspace chat.
2. Create an expense.
3. Delete the expense.
4. Navigate to Reports > Expenses.
5. In the search field, enter group-by:from status:deleted and search.
6. Click Columns, select "Action", and click Apply.
7. Expand the table row.
8. Observe the action button.

Expected: An "Undelete" button is displayed (since deleted expenses cannot be viewed).

tc5-view-instead-of-undelete.mov

---

TC-6: Selection mode persists after undeleting all expenses offline (mobile)

Issue: #86790
Platforms: Android App, iOS App

Steps:

1. Go to a workspace chat.
2. Create an expense.
3. Delete the expense.
4. Navigate to Reports > Expenses.
5. Filter by Status = Deleted and Apply.
6. Go offline.
7. Long-tap the expense > Select.
8. Tap dropdown > Undelete.

Expected: Selection mode exits automatically since there are no more expenses to display.

tc6-selection-mode.mov

---

TC-7: Undeleted expense does not load when undeleted and opened offline

Issue: #86793
Platforms: MacOS Chrome/Safari

Steps:

1. Go to a workspace chat.
2. Create an expense.
3. Delete the expense.
4. Navigate to Reports > Expenses.
5. Filter by Status = Deleted and Apply.
6. Go offline.
7. Select the expense via checkbox.
8. Click dropdown > Undelete.
9. Go to Inbox and open self DM.
10. Tap to open the undeleted expense.

Expected: The undeleted expense loads and displays correctly.

tc7-offline.mov

• Verify that no errors appear in the JS console

Offline tests

See TC-6 and TC-7

QA Steps

Same as Tests

• 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 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

android.mov

Android: mWeb Chrome

android-web.mov

iOS: Native

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	92.30% <ø> (ø)
...hList/ListItem/ActionCell/actionTranslationsMap.ts	100.00% <ø> (ø)
...ts/Search/SearchList/ListItem/ActionCell/index.tsx	68.42% <100.00%> (ø)
...h/SearchList/ListItem/ExpenseReportListItemRow.tsx	0.00% <ø> (ø)
...earch/SearchList/ListItem/ReportListItemHeader.tsx	97.14% <ø> (ø)
...mponents/Search/SearchList/ListItem/StatusCell.tsx	60.00% <100.00%> (ø)
...h/SearchList/ListItem/TransactionGroupListItem.tsx	71.91% <ø> (ø)
...SearchList/ListItem/UserInfoAndActionButtonRow.tsx	100.00% <ø> (ø)
src/components/Search/SearchList/index.tsx	44.06% <100.00%> (+0.47%)	⬆️
...ponents/TransactionItemRow/DataCells/TotalCell.tsx	80.00% <ø> (ø)
... and 15 more
... and 12 files with indirect coverage changes

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 040f009777

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[luacmartins]

@jnowakow how's this one coming along? Which bugs are left to be fixed?

[jnowakow]

@luacmartins I'm currently working on this one:

• [Due for payment 2026-04-14] Expense - Undeleted IOU expense shows negative amount #86788

Those two are discussed with Garret and Lucien:

• [Due for payment 2026-04-14] LHN - LHN shows original amount instead of split amount after undeleting expense #86782
• [Due for payment 2026-04-14] Reports - Deleted split expense does not show up when filtered with status:deleted #86835

Those are in the the queue

• [Due for payment 2026-04-14] Expense - Undeleted expense does not load when undeleted and opened offline #86793
• [Due for payment 2026-04-14] Expense - "Unheld the expense" message is shown after undeleting held expense #86799
• [Due for payment 2026-04-14] Expense - Selection mode persists after undeleting all expenses offline #86790

Those fixes for those issues are merged to this branch:

• [Due for payment 2026-04-14] Expense - Tapping on expense row does not deselect or select expense #86780
• [Due for payment 2026-04-14] Reports - Deleted expense with negative amount is not shown negative #86783
• [Due for payment 2026-04-14] Reports - Category column does not align with the table header #86791
• [Due for payment 2026-04-14] Reports - Non functional View button is shown instead of Undelete button #86796
• [Due for payment 2026-04-14] Reports - Merged expense appears when filtering by "Deleted" with the kept amount. #86850

And to this we agreed that it's not a bug:

• [Due for payment 2026-04-14] Reports - Merged expense appears when filtering by "Deleted" with the kept amount. #86850

[melvin-bot]

🎯 @rojiphil, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/608639.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

[jnowakow]

I'll resolve conflicts later in the day because they keeps popping up

[jnowakow]

Conflicts resolved, I hope there new conflicts won't appear before @luacmartins wakes up 🤞

[luacmartins]

LGTM

[luacmartins]

Nice! Thanks for the hard work @jnowakow @rojiphil! Let's hope we don't get any blockers this time around

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[github-actions]

🚧 @luacmartins has triggered a test Expensify/App build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #86938.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-c80f3ab-d10f585-86d3f2457de6cd2aa154228b2875e190c01d12d2/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-c80f3ab-d10f585-766d70d1b27189c417c8b10f9312027b4df74edd/index.html

Web 🕸️
https://86938.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.3.60-0 🚀

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

Bundle Size Analysis (Sentry):

• Android
• iOS

[MelvinBot]

Yes, help site changes are required. PR #86938 introduces deleted expense search and undelete functionality, which is not currently documented.

I've created a draft PR with the required updates: #88028

Changes made

How to Delete Expenses

• Added a new "How to find and undelete deleted expenses" section with step-by-step instructions
• Updated keywords and internalScope metadata to cover the undelete workflow

Getting Started with the Reports Page

• Added "Deleted" to the expense status filter examples

Expense and Report Actions

• Added Undelete to the secondary actions table

Note: I was unable to add the draft PR to GitHub project 196 due to permissions — please add it manually.

[jponikarchuk]

Deploy Blocker #88034 was identified to be related to this PR.

[mitarachim]

Deploy Blocker #88036 was identified to be related to this PR.

[jponikarchuk]

Deploy Blocker #88037 was identified to be related to this PR.

[mitarachim]

Deploy Blocker #88040 was identified to be related to this PR.

[nlemma]

Deploy Blocker #88073 was identified to be related to this PR.

[OSBotify]

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.60-22 🚀

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

[melvin-bot]

🤖 Payment issue created: #88398