Skip to content

Chat - Default avatars are shown in LHN instead of custom ones #30932

Closed

Description

@kbecciv

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: 1.3.96.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:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

  1. Go to staging.new.expensify.com or open Expensify App
  2. Login with any account
  3. Check user avatars in LHN

Expected Result:

Custom avatars are shown in LHN for users who have them

Actual Result:

Default avatars are shown in LHN for all users, even if custom ones are loaded

Workaround:

Unknown

Platforms:

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

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6266648_1699313780903.Chat-default-avatars-instead-custom.mp4

View all open jobs on GitHub

Activity

  1. OSBotify commented on Nov 6, 2023

    @OSBotify
    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.
  2. melvin-bot commented on Nov 6, 2023

    @melvin-bot

    Triggered auto assignment to @cead22 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  3. roryabraham commented on Nov 7, 2023

    @roryabraham
    Contributor

    Discussed in slack, but I think we can fix this by removing the call to _.values here

  4. cead22 commented on Nov 7, 2023

    @cead22
    Contributor

    I pushed a draft PR with another potential solution, in case we wanna go that route

  5. TMisiukiewicz commented on Nov 7, 2023

    @TMisiukiewicz
    Contributor

    Hi, I'm Tomasz from Callstack, seems like a regression from #30242 I've been working on together with @adhorodyski. I think solution proposed by @roryabraham is correct - I'll take care of creating the PR

  6. mountiny commented on Nov 7, 2023

    @mountiny
    Contributor

    gonna push this forwards now

  7. 5 remaining items

  8. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 7, 2023
  9. melvin-bot commented on Nov 7, 2023

    @melvin-bot

    Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  10. melvin-bot commented on Nov 7, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  11. mountiny commented on Nov 7, 2023

    @mountiny
    Contributor

    Fixed, we will have to pay @rushatgabhane for review

  12. rushatgabhane commented on Nov 12, 2023

    @rushatgabhane
    Member

    @mountiny what amount should I request on new dot?

  13. mountiny commented on Nov 13, 2023

    @mountiny
    Contributor

    I guess this would be $500 based on the classic rules

  14. rushatgabhane commented on Nov 17, 2023

    @rushatgabhane
    Member
  15. mountiny commented on Nov 20, 2023

    @mountiny
    Contributor

    I believe we can close this one now and the payer will come back here to confirm once request has been paid.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions