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-12-04] Chat - Blank avatar on LHN when starting chat with new user offline #75930
Version Number: 9.2.63-0 Reproducible in staging?: Y Reproducible in production?: N 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):djosijnoijsoijsoi@gmail.com Issue reported by: Applause - Internal Team
Action Performed:
Go to staging.new.expensify.com
Go offline
Go to FAB > Start chat
Enter email of new user and select it
Expected Result:
LHN will show fallback avatar
Actual Result:
LHN shows no avatar
Report view shows blank avatar instead of fallback avatar
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
👋 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.
changed the title [-]Chat - Blank avatar on LHN when starting chat with new user offline[/-][+][Due for payment 2025-12-04] Chat - Blank avatar on LHN when starting chat with new user offline[/+]on Nov 27, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.64-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@MonilBhavsar@greg-schroeder The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Nov 24, 2025
Triggered auto assignment to @greg-schroeder (
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.melvin-bot commentedon Nov 24, 2025
Triggered auto assignment to @MonilBhavsar (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Nov 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 Nov 24, 2025
💬 A slack conversation has been started in #expensify-open-source
marcaaron commentedon Nov 25, 2025
Seems possibly related to https://github.com/Expensify/App/pull/75371/files
IuliiaHerets commentedon Nov 25, 2025
Issue is not reproduced on Web and mWeb by QA team, build v9.2.63-1
MicrosoftTeams-video.9.mp4
2025-11-25.11-31-44.mp4
MonilBhavsar commentedon Nov 25, 2025
Thanks, closing!
melvin-bot commentedon Nov 25, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-]Chat - Blank avatar on LHN when starting chat with new user offline[/-][+][Due for payment 2025-12-04] Chat - Blank avatar on LHN when starting chat with new user offline[/+]melvin-bot commentedon Nov 27, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Nov 27, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.64-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-12-04. 🎊
melvin-bot commentedon Nov 27, 2025
@MonilBhavsar @greg-schroeder The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]