Expense - "Tracked $XX" remains on chat after moving remaining split to workspace.

[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.
Prerequisite 2: Account has at least one workspace.

1. Open the staging.new.expensify.com website.
2. Navigate to Self DM.
3. Create a manual expense.
4. Open the just created expense.
5. Click on "More" > "Split" > Save splits.
6. Right click and delete the split displayed at the bottom.
7. Open remaining split.
8. Click on report field > "Create Report"
9. Return to Self DM.
10. Note that "Tracked $XX" is displayed as a message in chat.
11. Delete the message.
12. Note that message remains but expense disappears from workspace chat.
13. Delete the message again.
14. Note that now, message disappears too.

Expected Result:

User should be able to move remaining split to workspace chat and no message should remain visible on Self DM.

Actual Result:

After deleting unreported split and moving remaining one to workspace, "Tracked $XX" appears as message in chat on Self DM. Deleting the message, makes the split disappears from workspace chat.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7221368_1785365238180.Self_Split_8.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7221368

[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/fe02344967061e2086a3396d8a0961b6ff705bc9ab9738a100f6856bd9af3d2f

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