[Due for payment 2025-04-28][$250] Reports - "Unavailable workspace" avatar is shown after paying invoice as business

[mitarachim]

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.26-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): dnhiusdhidushdi@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Search

Action Performed:

Precondition:

• User A has a workspace with invoicing enabled.
• User B does not have any workspace.
• User A and B do not have chat history with each other.

1. Go to staging.new.expensify.com
2. [User A] Send an invoice to User B.
3. [User B] Go to Reports > Chats.
4. [User B] Click Pay.
5. [User B] Click Pay as business > Pay elsewhere.
6. [User B] Hover over the unavailable workspace avatar.

Expected Result:

After paying the invoice as business, the new workspace avatar will be the workspace avatar.

Actual Result:

After paying the invoice as business, the new workspace avatar is "Unavailable workspace" avatar.
It renders the correct workspace avatar after a while.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6797789_1744256308863.20250410_112253.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021910253607525893166
• Upwork Job ID: 1910253607525893166
• Last Price Increase: 2025-04-10
• Automatic offers:
• brunovjk | Reviewer | 106864318

Issue Owner

Current Issue Owner: @lschurr

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @lschurr (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]

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

[MariaHCD]

I don't think this need to block the deploy.

It seems like this might be a scenario where we the optimistic data sets the workspace to the unavailable workspace but the once the API request succeeds, the correct workspace information is set.

For expected behavior, perhaps we only set the unavailable workspace if this action was taken offline?

cc: @cristipaval @davidcardoza