[Paid meow] Workspace - Duplicate expense preview avatar after workspace is deleted

[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: 9.0.41-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Create a new workspace
3. Submit an expense
4. Delete the workspace
5. Go to the workspace chat (now archived)

Expected Result:

The expense preview avatar will remain the same after the workspace is deleted

Actual Result:

The expense preview avatar changes after the workspace is deleted
It changes to stacked avatars with both avatars from the workspace

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

Bug6619463_1727626718511.bandicam_2024-09-30_00-15-25-899.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @OfstadC

[melvin-bot]

Triggered auto assignment to @mjasikowski (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Current assignee @mjasikowski is eligible for the DeployBlockerCash assigner, not assigning anyone new.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[mjasikowski]

Possibly related: #49403

[mjasikowski]

Reverting #49403 did not fix the issue, looking further

[mjasikowski]

Pinpointed the offending PR using git bisect: #49172

[mjasikowski]

@grgia would you be able to take a look at this and see if this can be easily fixed or reverted?

[grgia]

It's late for me let's revert #49172 for now

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[parasharrajat]

This was solved long back. I was C+ on the revert PR. Can we please assign someone from BZ to make the payment?

[melvin-bot]

This issue has not been updated in over 15 days. @mjasikowski, @grgia 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!

[mjasikowski]

This was solved long back. I was C+ on the revert PR. Can we please assign someone from BZ to make the payment?

@Expensify/bug-zero pinging you here

[melvin-bot]

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

[parasharrajat]

[Pay meow]

😹

[OfstadC]

Sorry friends! Looking now

[OfstadC]

Payment Summary

• @parasharrajat due $250 via manual New Expensify request

If i'm missing anyone, please let me know!

[parasharrajat]

Payment requested as per #49927 (comment)

[JmillsExpensify]

$250 approved for @parasharrajat