Skip to content

[HOLD for payment 2024-11-29] [$250] Group chat - New member is displayed with offline profile avatar #52639

Closed

Description

@IuliiaHerets

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.0.63-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5229966&group_by=cases:section_id&group_id=296760&group_order=asc
Email or phone of affected tester (no customers): gocemate+a2862@gmail.com
Issue reported by: Applause Internal Team

Action Performed:

  1. Create group conversation with few members
  2. Click on header> Members> Invite new member
  3. Enter email address and take a look at user's avatar

Expected Result:

User should have default or custom profile avatar

Actual Result:

User is displayed with offline profile avatar when invite it in existing group chat

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Bug6666563_1731690502328.Recording__4536.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021858590656610669336
  • Upwork Job ID: 1858590656610669336
  • Last Price Increase: 2024-11-18
  • Automatic offers:
    • brunovjk | Reviewer | 104980522
    • gijoe0295 | Contributor | 104980525
Issue OwnerCurrent Issue Owner: @garrettmknight

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 15, 2024
  2. melvin-bot commented on Nov 15, 2024

    @melvin-bot

    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.

  3. gijoe0295 commented on Nov 15, 2024

    @gijoe0295
    Contributor

    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 through SearchForReport API.

    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, call SearchForReport same as RoomInvitePage:

    useEffect(() => {
    UserSearchPhraseActions.updateUserSearchPhrase(debouncedSearchTerm);
    ReportActions.searchInServer(debouncedSearchTerm);
    }, [debouncedSearchTerm]);

    useEffect(() => {
    UserSearchPhraseActions.updateUserSearchPhrase(debouncedSearchTerm);
    }, [debouncedSearchTerm]);

    Report.searchInServer(debouncedSearchTerm);
  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Nov 18, 2024
  5. 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
  6. melvin-bot commented on Nov 18, 2024

    @melvin-bot
  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Nov 18, 2024
  8. moved this to Bugs and Follow Up Issues in #expensify-bugson Nov 18, 2024
  9. melvin-bot commented on Nov 18, 2024

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @brunovjk (External)

  10. 22 remaining items

  11. melvin-bot commented on Nov 22, 2024

    @melvin-bot

    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:

  12. melvin-bot commented on Nov 22, 2024

    @melvin-bot

    @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]

  13. brunovjk commented on Nov 28, 2024

    @brunovjk
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 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:

    1. Go to a group chat
    2. Click on header > Members > Invite new member
    3. Enter an email that hasn't been chatted with but should already exist
    4. Verify his contact not show fallback avatar (it can show fallback avatar briefly while it's fetching data)

    Do we agree 👍 or 👎

  14. melvin-bot commented on Dec 2, 2024

    @melvin-bot

    @deetergp, @garrettmknight, @brunovjk, @gijoe0295 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  15. garrettmknight commented on Dec 2, 2024

    @garrettmknight
    Contributor

    All paid out, closing!

  16. moved this from Bugs and Follow Up Issues to Done in #expensify-bugson Dec 2, 2024
  17. moved this from Done to Bugs and Follow Up Issues in #expensify-bugson Dec 2, 2024
  18. moved this from Bugs and Follow Up Issues to Hold for Payment in #expensify-bugson Dec 3, 2024
  19. moved this from Hold for Payment to Done in #expensify-bugson Feb 4, 2025
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.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions