Skip to content

LHN - GBR is displayed on LHN when paying a user #62361

Closed

Description

@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: v9.1.47-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: exp #60267
Email or phone of affected tester (no customers): expensify416+da2@gmail.com
Issue reported by: Applause Internal Team
Device used: macOS chrome 14.2, mWeb, Android, Desktop
App Component: Left Hand Navigation (LHN)

Action Performed:

  1. Open ND staging
  2. Click on FAB > Start Chat > Select a user
  3. Click on + in composer > Pay > Enter amount > Next > Pay elsewhere

Expected Result:

There shouldn't be GBR on LHN

Actual Result:

GBR is displayed on LHN

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6836965_1747738296698.Screen_Recording_2025-05-20_at_1.45.52_in_the_afternoon.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 20, 2025
  2. melvin-bot commented on May 20, 2025

    @melvin-bot

    Triggered auto assignment to @johncschuster (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. Tony-MK commented on May 20, 2025

    @Tony-MK
    Contributor

    Backend bug since sendMoneyElsewhere returns hasOutstandingChildRequest as true.

    Maybe it's supposed to return the onyx merge to the receiver only.

    Image

  4. added
    InternalRequires API changes or must be handled by Expensify staff
    on May 27, 2025
  5. johncschuster commented on May 27, 2025

    @johncschuster
    Contributor

    Triaging!

  6. melvin-bot commented on Jun 2, 2025

    @melvin-bot

    @johncschuster Huh... This is 4 days overdue. Who can take care of this?

  7. melvin-bot commented on Jun 3, 2025

    @melvin-bot

    @johncschuster this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  8. johncschuster commented on Jun 3, 2025

    @johncschuster
    Contributor

    No one has picked this one up yet. I'll raise it in the AM

  9. 5 remaining items

  10. melvin-bot commented on Jun 16, 2025

    @melvin-bot

    @johncschuster Huh... This is 4 days overdue. Who can take care of this?

  11. melvin-bot commented on Jun 18, 2025

    @melvin-bot

    @johncschuster Still overdue 6 days?! Let's take care of this!

  12. johncschuster commented on Jun 18, 2025

    @johncschuster
    Contributor

    I didn't realize Hot Pick made these ready issues more discoverable to our internal engineers. Applied it to the issue!

  13. self-assigned this
    on Jun 20, 2025
  14. removed
    Hot PickReady for an engineer to pick up and run with
    on Jun 20, 2025
  15. cristipaval commented on Jun 20, 2025

    @cristipaval
    Contributor

    taking over this one

  16. cristipaval commented on Jun 20, 2025

    @cristipaval
    Contributor

    PR in review.

  17. johncschuster commented on Jun 24, 2025

    @johncschuster
    Contributor

    Not overdue, Melv

  18. cristipaval commented on Jun 24, 2025

    @cristipaval
    Contributor

    This is fixed.

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.DailyKSv2InternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions