[LOW] [Splits] [$500] [MEDIUM] Web - IOU - Receipt from manual request remains on Admins account when Employee delete it

[lanitochka17]

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: 1.4.32-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

1. Employee creates manual request on collect workspace chat
2. Employee add a receipt to IOU
3. Employee delete the receipt
4. Admin open the IOU request

Expected Result:

Receipt should be not presented on Admin's side

Actual Result:

After deletion receipt is still present until refresh the page

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6355227_1706222212610.Recording__1932.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~014fe31ab963ba8b49
• Upwork Job ID: 1750654064488505344
• Last Price Increase: 2024-02-15

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @MitchExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

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

[lanitochka17]

We think that this bug might be related to #wave5.
CC @dylanexpensify

[bernhardoj]

Looks like the pusher doesn't send an update to remove the receipt

[MitchExpensify]

Wave 5 worthy @dylanexpensify ?

[MitchExpensify]

Friendly bump @dylanexpensify

[melvin-bot]

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

[melvin-bot]

@allroundexperts, @MitchExpensify Huh... This is 4 days overdue. Who can take care of this?

[MitchExpensify]

Checking in with @dylanexpensify 👀

[dylanexpensify]

DMing back!

[rezkiy37]

Hi, I’m Michael (Mykhailo) from Callstack and I would like to work on this issue.

[melvin-bot]

@allroundexperts @MitchExpensify this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[melvin-bot]

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

[rezkiy37]

I've investigated the bug. I can confirm that it is still replicable. I see that we actively use the Pusher for this logic. So, the Pusher does not send an update for an admin, when a member removed a receipt. Also, even after a re-fetching data, it is does not overwrite a receipt property of a transaction. It resets a filename property, but it is not enough.
So, after this, I can say that someone should handle this from the backend side.

Receipt.Bug.mp4

[rezkiy37]

As Vit said before #35208 (comment). Looks like that's an internal issue for the internal devs.

[MitchExpensify]

We either do not push the updates correctly (internal) or we do not re-render the UI based on the updated data correctly (and you need to refresh)

@mountiny do you have any bandwidth to check this out?

[mountiny]

Not at the moment, still focusing on Wave collect release 1

[rezkiy37]

Should we mark this issue as "On Hold"?

[mountiny]

Why on hold? Its ready to be investigated, I have added the Hot Pick label

[rezkiy37]

Ah, good. I misunderstood this comment.

[MitchExpensify]

Waiting on Internal volunteer, Melvin

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[MitchExpensify]

I was unable to reproduce this on v1.4.62-8

[rezkiy37]

Hey!
I just wanted to let you know about my vacation for next week. I will be back on 06.05.2024. Meanwhile, I asked @waterim to take over this issue.
See you soon!

[MitchExpensify]

@waterim Are you able to reproduce this> I am not currently able to

[mvtglobally]

Issue not reproducible during KI retests. (Second week)

[mvtglobally]

Issue not reproducible during KI retests. (Third week)