Skip to content

[Due for payment 2025-10-22] [$250] Chat - "Chat report" is displayed when starting a new chat with non-existing account #71209

Closed

Description

@nlemma

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.2.17-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): htad26+eury@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 10/Chrome, iPhone/Chrome
App Component: Chat Report View

Action Performed:

  1. Sign in with a new account
  2. FAB > Start chat
  3. Enter the email of a non existing user
  4. Select it
  5. Observe the email before the RHP is closed

Expected Result:

Only the email of the user should be displayed

Actual Result:

"Chat Report" is displayed along with the email of the user

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

Bug6954557_1758723367469.2025-09-24_17_03_00.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021970932699923195040
  • Upwork Job ID: 1970932699923195040
  • Last Price Increase: 2025-09-24
  • Automatic offers:
    • thelullabyy | Contributor | 109057894
Issue OwnerCurrent Issue Owner: @NicMendonca

Activity

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

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (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. github-actions commented on Sep 24, 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.
  4. melvin-bot commented on Sep 24, 2025

    @melvin-bot

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

  5. melvin-bot commented on Sep 24, 2025

    @melvin-bot

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

  6. AndrewGable commented on Sep 24, 2025

    @AndrewGable
  7. AndrewGable commented on Sep 24, 2025

    @AndrewGable
    Contributor

    @dangrous is looking at a revert locally to confirm this is the right PR.

  8. 46 remaining items

  9. added a commit that references this issue on Oct 21, 2025
  10. brunovjk commented on Oct 21, 2025

    @brunovjk
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: brunovjk@1f0f3dc#r168356586

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion:

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    Regression Test Proposal

    Test:

    1. Sign in with a new account
    2. FAB > Start chat
    3. Enter the email of a non existing user
    4. Select it
    5. Observe the email before the RHP is closed
    6. Verify only email of the user is displayed

    Do we agree 👍 or 👎

  11. melvin-bot commented on Oct 22, 2025

    @melvin-bot

    Issue is ready for payment but no BZ is assigned. @NicMendonca you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!

  12. melvin-bot commented on Oct 27, 2025

    @melvin-bot

    @thelullabyy Eep! 4 days overdue now. Issues have feelings too...

  13. NicMendonca commented on Oct 29, 2025

    @NicMendonca
    Contributor

    Payment Summary

    Contributor: @thelullabyy paid $250 via Upwork (done ✅ )
    Contributor+: @brunovjk due $250 via NewDot

  14. garrettmknight commented on Nov 1, 2025

    @garrettmknight
    Contributor

    $250 approved for @brunovjk

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions