Expense - Deleted unreported split reappears when user turns to offline mode.

[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: Pull Request QA execution
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. Open the just created expense.
5. Click on "More" > "Split" > Save splits.
6. Return to chat.
7. Right click and delete both splits.
8. Turn to offline mode.
9. Note that deleted split reappears in chat when user is in offline mode.
10. Turn to online mode.
11. Note that split disappears again.

Expected Result:

Deleted splits shouldn´t reappear when user is in offline mode.

Actual Result:

Deleted split becomes visible again when user turns to offline mode.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7221286_1785360059649.Deleted_Split.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7221286

[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/60398abd67c956ee2a13ee5d6fdc6b805ef68b7220c87f64dda509a443089f0c

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