Invoice - Unavailable workspace avatar after paying elsewhere as a business

[vincdargento]

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

---

Issue was found while executing QA for PR #60034

Version Number: v9.1.28-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #60034
Email or phone of affected tester (no customers): testpayment935@gmail.com
Issue reported by: Applause Internal Team
Device used: Web, mWeb, Android
App Component: Chat Report View

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. [User A] Send an invoice to User B.
   2.[User B] Go to invoice in the chat
   3.[User B] Click Pay.
   4.[User B] Click Pay as business > Pay elsewhere.
   5.Notice that one of workspace avatar is changed to invoice when hovering over the avatar.

Expected Result:

Both avatar is displayed when hovering over the avatar.

Actual Result:

Workspace avatar is changed to invoice when hovering over the avatar.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

[melvin-bot]

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

[vincdargento]

@maddylewis FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[brunovjk]

Investigating. @rezkiy37 do you have any idea what might be causing this issue? Thanks.

[AndrewGable]

@brunovjk - Can you send a revert PR for #60034 please?