Skip to content

LHN - Concierge does not show sender in LHN but it shows "Expensify" in search result #58943

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: 9.1.17-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
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): applausetester+kok1@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to Concierge.
  3. Open search router.
  4. Search for Concierge if needed.

Expected Result:

Both LHN and the report preview in the search result should be consistent when showing the sender.

Actual Result:

Concierge chat in LHN does not show the sender, while the report preview in search result shows the sender as "Expensify".

This issue also applies when message receiver compares the received message in LHN preview and search result preview.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6778817_1742622382190.20250322_134032.mp4
Image

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @nkdengineer

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    DeployBlockerCashThis issue or pull request should block deployment
    on Mar 22, 2025
  2. melvin-bot commented on Mar 22, 2025

    @melvin-bot

    Triggered auto assignment to @OfstadC (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 Mar 22, 2025

    @melvin-bot

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

  4. melvin-bot commented on Mar 22, 2025

    @melvin-bot

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

  5. github-actions commented on Mar 22, 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. removed
    DeployBlockerIndicates it should block deploying the API
    on Mar 24, 2025
  7. 17 remaining items

  8. techievivek commented on Mar 27, 2025

    @techievivek
    Contributor

    @nkdengineer Assigned the GH to you.

  9. shawnborton commented on Mar 27, 2025

    @shawnborton
    Contributor

    Correct

  10. nkdengineer commented on Mar 27, 2025

    @nkdengineer
    Contributor

    Thanks everyone, I'll open a follow up PR soon

  11. shawnborton commented on Mar 27, 2025

    @shawnborton
    Contributor

    Thanks @nkdengineer!

  12. melvin-bot commented on Apr 21, 2025

    @melvin-bot

    This issue has not been updated in over 15 days. @OfstadC, @techievivek, @nkdengineer eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  13. OfstadC commented on Jun 3, 2025

    @OfstadC
    Contributor

    Please note i'll be OoO through Friday - If something needs BZ - please add another BZ member

  14. melvin-bot commented on Jun 18, 2025

    @melvin-bot

    @OfstadC, @techievivek, @nkdengineer, this Monthly task hasn't been acted upon in 6 weeks; closing.

    If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

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

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions