Skip to content

Invoice - Unavailable workspace avatar after paying elsewhere as a business #60281

Closed

Description

@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

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 15, 2025
  2. melvin-bot commented on Apr 15, 2025

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

  3. melvin-bot commented on Apr 15, 2025

    @melvin-bot

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

  4. melvin-bot commented on Apr 15, 2025

    @melvin-bot

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

  5. github-actions commented on Apr 15, 2025

    @github-actions
    Contributor

    👋 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.
  6. vincdargento commented on Apr 15, 2025

    @vincdargento
    Author

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

  7. brunovjk commented on Apr 15, 2025

    @brunovjk
    Contributor

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

  8. AndrewGable commented on Apr 15, 2025

    @AndrewGable
    Contributor

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

  9. brunovjk commented on Apr 15, 2025

    @brunovjk
    Contributor

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

    Sure, but I'm in college now. I get home at 4h PST. Can we wait?

  10. AndrewGable commented on Apr 15, 2025

    @AndrewGable
    Contributor

    Ah no worries, I can prepare the revert, we can work to fix this issue in a new PR 👍

  11. brunovjk commented on Apr 15, 2025

    @brunovjk
    Contributor

    Thank you @AndrewGable 🚀

  12. rezkiy37 commented on Apr 15, 2025

    @rezkiy37
    Contributor

    Hi, I am Michael (Mykhailo) from Callstack, an expert agency and I can work on this issue.

  13. AndrewGable commented on Apr 15, 2025

    @AndrewGable
    Contributor

    Hey @rezkiy37 - We are going to revert the original PR and you can work on fixing it up in a follow up PR. Thanks!

  14. rezkiy37 commented on Apr 15, 2025

    @rezkiy37
    Contributor

    @AndrewGable, got it. I am working on it!

  15. brunovjk commented on Apr 15, 2025

    @brunovjk
    Contributor

    @AndrewGable do you want assign me as C+? Or isn't necessary?

  16. AndrewGable commented on Apr 15, 2025

    @AndrewGable
    Contributor

    Not necessary for now, we have deployed the revert to staging and are just doing final testing now.

  17. AndrewGable commented on Apr 15, 2025

    @AndrewGable
    Contributor

    Confirmed that expected result now appears 👍

    Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions