[$250] [Due for payment 2025-05-08] Track expense - "moved this expense to" message shows "unavailable workspace" in offline mode

[lanitochka17]

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.33-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: #60688
Email or phone of affected tester (no customers): sojsosjds@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• Account has self DM

1. Go to staging.new.expensify.com
2. Go to self DM
3. Submit a manual expense in self DM
4. Go offline
5. Click Share it with my account
6. Select a workspace if the account has a workspace
7. Enter merchant and select a category
8. Click Create expense
9. Close invite member RHP
10. Go to transaction thread

Expected Result:

"moved this expense to" system message will not show "unavailable workspace"

Actual Result:

"moved this expense to" system message shows "unavailable workspace owes -x"

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6815651_1745873170079.20250429_044214.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021922258579568338310
• Upwork Job ID: 1922258579568338310
• Last Price Increase: 2025-05-13

Issue Owner

Current Issue Owner: @

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

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

[melvin-bot]

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

[tgolen]

@waterim Could you help me look into this one? It looks like it affects a message that you've recently been working on.

[luacmartins]

Got a PR to fix this here