[HOLD for payment 2025-02-04] [$250] Search - Expense from the list does not disappear after deletion

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.72-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5309274
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

1. Open HybridApp
2. Log in to the HT account
3. Send 2 manual expenses to any user
4. Go to Search -> Expenses -> All
5. Delete one of the created expenses from step 3
6. Tap again on the deleted expense

Expected Result:

After deleting an expense, it should immediately disappear from the list without refreshing the page

Actual Result:

Expense from the list does not disappear after deletion

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6685819_1733443178341.ScreenRecording_12-06-2024_04-50-37_1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021865183017070238528
• Upwork Job ID: 1865183017070238528
• Last Price Increase: 2024-12-13
• Automatic offers:
• rayane-djouah | Reviewer | 105373332
• FitseTLT | Contributor | 105373334

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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.

[daledah]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Expense from the list does not disappear after deletion

What is the root cause of that problem?

In useSearchHighlightAndScroll, we only update Search data if new transaction is added, not when a transaction is deleted:

App/src/hooks/useSearchHighlightAndScroll.ts

Line 42 in b9107bf

if (transactionsLength && typeof previousTransactionsLength === 'number' && transactionsLength > previousTransactionsLength) {

What changes do you think we should make in order to solve the problem?

Change condition to update Search data if number of transaction is different:

App/src/hooks/useSearchHighlightAndScroll.ts

Line 42 in b9107bf

if (transactionsLength && typeof previousTransactionsLength === 'number' && transactionsLength > previousTransactionsLength) {

        if (transactionsLength && typeof previousTransactionsLength === 'number' && transactionsLength !== previousTransactionsLength) {

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

[FitseTLT]

Edited by proposal-police: This proposal was edited at 2024-12-06 15:01:26 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

Search - Expense from the list does not disappear after deletion

What is the root cause of that problem?

We only send search request if there is an increase in transaction length, i.e. the currentTransaction length is greater than the previous transaction length

App/src/hooks/useSearchHighlightAndScroll.ts

Line 42 in b9107bf

if (transactionsLength && typeof previousTransactionsLength === 'number' && transactionsLength > previousTransactionsLength) {

but here we are deleting the expense that will decrease the transactions length we have

What changes do you think we should make in order to solve the problem?

The conditions that depend on transaction length are incorrect in both

App/src/hooks/useSearchHighlightAndScroll.ts

Line 42 in b9107bf

if (transactionsLength && typeof previousTransactionsLength === 'number' && transactionsLength > previousTransactionsLength) {

App/src/hooks/useSearchHighlightAndScroll.ts

Line 37 in b9107bf

if (searchTriggeredRef.current || previousTransactionsLength === transactionsLength) {

because transaction length equality can even mean there is a change that needs a search request to be sent. For instance, if a user creates a new expense but deletes another expense which could result in the transaction lengths to be equal but still there is a change that requires a fetch.
We should instead depend on a condition where the previous and current transaction IDs list are not equal (of course with deep comparison between the values they hold)

App/src/hooks/useSearchHighlightAndScroll.ts

Lines 76 to 80 in b9107bf

	const previousTransactionIDs = extractTransactionIDsFromSearchResults(previousSearchResults);
	const currentTransactionIDs = extractTransactionIDsFromSearchResults(searchResults.data);
	// Find new transaction IDs that are not in the previousTransactionIDs and not already highlighted
	const newTransactionIDs = currentTransactionIDs.filter((id) => !previousTransactionIDs.includes(id) && !highlightedTransactionIDs.current.has(id));

const previousTransactionIDs = previousTransactions && Object.keys(previousTransactions);
        const transactionIDs = transactions && Object.keys(transactions);

and replace this with it

App/src/hooks/useSearchHighlightAndScroll.ts

Line 42 in b9107bf

if (transactionsLength && typeof previousTransactionsLength === 'number' && transactionsLength > previousTransactionsLength) {

if(!isEqual(transactionIDs, previousTransactionIDs))

we can optionally add more condition of the existence of previous transaction ids and current transactionIDs to exclude the case where the values are undefined on first render 👍
and remove the condition here

App/src/hooks/useSearchHighlightAndScroll.ts

Line 37 in b9107bf

if (searchTriggeredRef.current || previousTransactionsLength === transactionsLength) {

        if (searchTriggeredRef.current) {

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

We can render the Search page (or optionally test only useSearchHighlightAndScroll) and change the transaction list from onyx by replacing a transaction with another one and mock our SearchActions.search and assert that it has been called 👍

What alternative solutions did you explore? (Optional)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021865183017070238528

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @rayane-djouah (External)

[mallenexpensify]

@rayane-djouah can you attempt reproduction and, if you're able to, review the above proposals? I tried to test and staging.new.expensify.com froze for me :/

[rayane-d]

Reproducible

Screen.Recording.2024-12-10.at.1.52.09.AM.mov

[rayane-d]

For instance, if a user creates a new expense but deletes another expense which could result in the transaction lengths to be equal but still there is a change that requires a fetch.

@FitseTLT Is the user currently able to create a new expense and delete another one at the same time?

[rayane-d]

@luacmartins would you like to be assigned to this one as CME since it's related to the search project?

[FitseTLT]

For instance, if a user creates a new expense but deletes another expense which could result in the transaction lengths to be equal but still there is a change that requires a fetch.

@FitseTLT Is the user currently able to create a new expense and delete another one at the same time?

@rayane-djouah We are not only tracking the creation/deletion of transactions created by the current user, for instance, another user member of the current user's workspace can create an expense and delete another one and when the update of transaction reaches the current user's onyx the transaction length will be equal that's what I am indicating.

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[rayane-d]

Will review today

[melvin-bot]

@luacmartins, @mallenexpensify, @rayane-djouah Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[rayane-d]

@luacmartins - Some thoughts:

• Search - Highlight newly added expense #49192 added the logic to trigger the search command and highlight the newly added expense when adding a new expense from the search page, as requested in, as requested in [HOLD for payment 2024-10-11] [HOLD for payment 2024-10-10] [$250] [Search v2.2] Reload the page and highlight the newly added expense when adding a new expense from the search page #48716
• Triggering the search command when deleting expenses from the search page wasn't considered in the initial design.
• @daledah's proposal correctly identifies the cause and addresses the deletion issue (by checking if the number of transactions has decreased), but it doesn't handle cases where a transaction is replaced in Onyx (since the transaction count remains the same).
• @FitseTLT proposal covers the case where a transaction is replaced in Onyx by performing a deep comparison of the previous and current transaction IDs.
• @FitseTLT also suggested adding unit tests.
• Since useSearchHighlightAndScroll initially focused only on highlighting and scrolling for newly added transactions, we may need to rename it or add comments to clarify that it now also handles transaction deletions.

I think we can go with @FitseTLT proposal

🎀👀🎀 C+ reviewed

[FitseTLT]

@luacmartins I am a bit confused here. Currently useSearchHighlightAndScroll hook checks for a change in transactions_ key and send search request accordingly. Now the problem we are facing is transactions_ key is not being correctly updated on deleting the last transaction in a report I was hoping to get that transactions_ key update fixed on this case so that the normal operation of the hook will work for this case too.
I am not sure how the BE code works but I don't think fixing the response of DeleteRequest API only suffice but also the data it pushes too for other users that didn't delete the money request. Like User A deleted a request in workspace that is owned by UserB and now the update doesn't reach for both users.

[luacmartins]

@FitseTLT yes, the data is being pushed to other users, but for some reason we're not returning it in the http response to the caller. So my PRs are adding all the onyxData updates to the http response. Does that make sense?

[FitseTLT]

@FitseTLT yes, the data is being pushed to other users, but for some reason we're not returning it in the http response to the caller. So my PRs are adding all the onyxData updates to the http response. Does that make sense?

Yep. But if you want to test you can do with branch of the PR because the BE change should solve it without any more FE change 👍

[luacmartins]

@FitseTLT doesn't seem to work. Check out the video below:

Screen.Recording.2025-01-10.at.1.44.26.PM.mov

[FitseTLT]

@luacmartins Did you apply any BE changes? Because now it is working I remember invoice deletion was not updated too but it is working now.

2025-01-11.00-10-20.mp4

2025-01-11.00-07-46.mp4

[luacmartins]

No BE changes that I'm aware of.

[FitseTLT]

No BE changes that I'm aware of.

Ok but now the BE is correctly updating transactions_ list so it seems fixed. I will work on the rest of the tasks left but let u know if any BE change is needed. Maybe some other BE PR might have fixed it Thx 👍

[melvin-bot]

This issue has not been updated in over 15 days. @luacmartins, @mallenexpensify, @FitseTLT, @rayane-djouah eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[rayane-d]

PR under review

[rayane-d]

PR is merged

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.89-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Fix - Search - Expense from the list does not disappear after deletion #54407

If no regressions arise, payment will be issued on 2025-02-04. 🎊

For reference, here are some details about the assignees on this issue:

• @FitseTLT requires payment automatic offer (Contributor)
• @rayane-djouah requires payment automatic offer (Reviewer)

[melvin-bot]

@rayane-djouah @mallenexpensify @rayane-djouah 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]

[rayane-d]

BugZero Checklist:

• Classify the bug:

Bug classification

Source of bug:

• 1a. Result of the original design (eg. a case wasn't considered)
• 1b. Mistake during implementation
• 1c. Backend bug
• 1z. Other:

Where bug was reported:

• 2a. Reported on production
• 2b. Reported on staging (deploy blocker)
• 2c. Reported on a PR
• 2z. Other:

Who reported the bug:

• 3a. Expensify user
• 3b. Expensify employee
• 3c. Contributor
• 3d. QA
• 3z. Other:

• The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

  Link to comment: N/A - This is a new feature (Result of the original design)

• If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

  Link to discussion: N/A

• If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

• [@mallenexpensify] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

  Link to issue:

Regression Test Proposal

#### Precondition:

- Create some expenses if none exist.

#### Test:

1. Go to the Search page.
2. Select and delete an expense.
3. Verify the deleted expense is immediately removed from the search list without refreshing the page.

Do we agree 👍 or 👎

[melvin-bot]

📣 @rayane-d! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[mallenexpensify]

Contributor: @FitseTLT paid $250 via Upwork
Contributor+: @rayane-d paid $250 via Upwork

Test case - https://github.com/Expensify/Expensify/issues/467599

Thx!