Expense -Deleted split remains in Self DM with infinite loading after being deleted on Spend

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.46-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #92055
Email or phone of affected tester (no customers): ibellicotest+2766@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has Self DM.

1. Open the staging.new.expensify.com website.
2. Navigate to Self DM.
3. Create a manual expense.
4. Navigate to "Spend" > "Expenses"
5. Select the just created expense.
6. Click on dropdown menu > "Split" > Save splits.
7. Select one of the splits and delete it.
8. Select the remaining split and delete it too.
9. Navigate to Self DM.
10. Note that an expense preview with infinite loading is visible.
11. Open the expense.
12. Note that "It´s not here" page opens.
13. Return to chat and delete expense.
14. Note that now, expense disappears.

Expected Result:

Split deleted while on "Spend", should automatically disappear from chat too.

Actual Result:

Split deleted while on "Spend", remains in Self DM showing infinite loading on preview and leads to "It´s not here" page.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7221341_1785363236415.Deleted_Split_1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Vincenzo Godoy
Bug ID: 7221341

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/a978ba3b6cb2a49094d9f5675bec46914466e0a67ca29b3c3a58b1ceab0021cb

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #92055

[melvin-bot]

@lakchote @dmkt9 you have been assigned to this deploy blocker because you reviewed the offending PR: #92055

[melvin-bot]

@ZhenjaHorbach you have been assigned to this deploy blocker because you authored the offending PR: #92055

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[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.