[Due for payment 2025-03-28] [Change Policy] LHN - "Workspace owes.." is displayed for the old workspace after moving the report

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.1.13-4
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: #57553
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: iPhone 15 iOs 18.3.1
App Component: Left Hand Navigation (LHN)

Action Performed:

1. Launch app and sign in as a gmail user
2. Create two workspaces, create an expense report with 2 expenses in the workspace chat 1
3. Send the url of the report to any chat, append /change-workspace to the URL
4. Tap on the new link
5. From the workspace selection list select Workspace 2.
6. Tap "Got it" on the educational modal
7. Navigate to LHN and observe the messages displayed for the workspace 1 and 2

Expected Result:

Owed amount for the expense report is shown only for the workspace 2, where the report was moved to.

Actual Result:

LHN for both workspace 1 (old ws) and workspace 2 (new ws) shows the same owed amount. Message "WS 1 owes $.." is removed after opening the workspace chat.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6770792_1741970238846.ScreenRecording_03-14-2025_9.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @alexpensify

[melvin-bot]

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

[melvin-bot]

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

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