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
[HOLD for payment 2024-11-29] [$250] Group chat - New member is displayed with offline profile avatar #52639
changed the title [-]Group chat - New member is displayed with offline profile avatar[/-][+][$250] Group chat - New member is displayed with offline profile avatar[/+]on Nov 18, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.65-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@brunovjk@garrettmknight@brunovjk 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]
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production
2b. Reported on staging (deploy blocker)
2c. Reported on both staging and production
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other: Applause Internal Team
[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: No PR directly added the bug, there was a detail missed during the implementation of the page.
[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
Precondition: Must be online.
Test:
Go to a group chat
Click on header > Members > Invite new member
Enter an email that hasn't been chatted with but should already exist
Verify his contact not show fallback avatar (it can show fallback avatar briefly while it's fetching data)
Activity
melvin-bot commentedon Nov 15, 2024
Triggered auto assignment to @garrettmknight (
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.gijoe0295 commentedon Nov 15, 2024
Edited by proposal-police: This proposal was edited at 2024-11-15 18:12:12 UTC.
Proposal
Please re-state the problem that we are trying to solve in this issue.
User is displayed with offline profile avatar when invite it in existing group chat
What is the root cause of that problem?
In
NewChatPage, we retrieved the personal details data, specifically avatar, from the BE throughSearchForReportAPI.But in
InviteReportParticipantsPage, we only get the details from Onyx.What changes do you think we should make in order to solve the problem?
In
InviteReportParticipantsPage, callSearchForReportsame asRoomInvitePage:App/src/pages/RoomInvitePage.tsx
Lines 238 to 241 in c3c7c7a
App/src/pages/InviteReportParticipantsPage.tsx
Lines 58 to 60 in c3c7c7a
[-]Group chat - New member is displayed with offline profile avatar[/-][+][$250] Group chat - New member is displayed with offline profile avatar[/+]melvin-bot commentedon Nov 18, 2024
Job added to Upwork: https://www.upwork.com/jobs/~021858590656610669336
melvin-bot commentedon Nov 18, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @brunovjk (
External)22 remaining items
melvin-bot commentedon Nov 22, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.65-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 2024-11-29. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Nov 22, 2024
@brunovjk @garrettmknight @brunovjk 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]
brunovjk commentedon Nov 28, 2024
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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: No PR directly added the bug, there was a detail missed during the implementation of the page.
[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
Precondition: Must be online.
Test:
Do we agree 👍 or 👎
melvin-bot commentedon Dec 2, 2024
@deetergp, @garrettmknight, @brunovjk, @gijoe0295 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
garrettmknight commentedon Dec 2, 2024
All paid out, closing!