You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-10-22] [$250] Chat - "Chat report" is displayed when starting a new chat with non-existing account #71209
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:
Sign in with a new account
FAB > Start chat
Enter the email of a non existing user
Select it
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
👋 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:
Identify the pull request that introduced this issue and revert it.
[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.
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!
Activity
melvin-bot commentedon Sep 24, 2025
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.github-actions commentedon Sep 24, 2025
👋 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:
melvin-bot commentedon Sep 24, 2025
Triggered auto assignment to @AndrewGable (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 24, 2025
💬 A slack conversation has been started in #expensify-open-source
AndrewGable commentedon Sep 24, 2025
AndrewGable commentedon Sep 24, 2025
@dangrous is looking at a revert locally to confirm this is the right PR.
46 remaining items
fix broken merge again
brunovjk commentedon Oct 21, 2025
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:
Do we agree 👍 or 👎
melvin-bot commentedon Oct 22, 2025
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!
melvin-bot commentedon Oct 27, 2025
@thelullabyy Eep! 4 days overdue now. Issues have feelings too...
NicMendonca commentedon Oct 29, 2025
Payment Summary
Contributor: @thelullabyy paid $250 via Upwork (done ✅ )
Contributor+: @brunovjk due $250 via NewDot
garrettmknight commentedon Nov 1, 2025
$250 approved for @brunovjk