Skip to content

[HOLD for payment 2024-06-06] [HOLD for payment 2024-05-06] [HOLD for payment 2024-05-03] Quick action - Fallback avatar is displayed on quick action after user avatar loads #40996

Closed

Description

@lanitochka17

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.4.66-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): natnael.expensify+3@gmail.com
Issue reported by: Applause - Internal Team

Issue found when executing PR #39229

Action Performed:

  1. Go to staging.new.expensify.com
  2. Submit a request to a user you haven't chatted with before
  3. Click on 'FAB'

Expected Result:

Avatar on quick action should be similar to the one loaded on report and LHN of the new user

Actual Result:

Avatar on quick action remained to be a fallback avatar

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

Add any screenshot/video evidence

Bug6461684_1714056035909.Screen_Recording_2024-04-25_at_4.58.23_in_the_afternoon.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @Christinadobrzyn

Activity

  1. melvin-bot commented on Apr 25, 2024

    @melvin-bot

    Triggered auto assignment to @flodnv (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  2. github-actions commented on Apr 25, 2024

    @github-actions
    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.
  3. lanitochka17 commented on Apr 25, 2024

    @lanitochka17
    Author

    @flodnv FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

  4. ZhenjaHorbach commented on Apr 25, 2024

    @ZhenjaHorbach
    Contributor

    I think it's dupe

    #40536

    Because they have the same root cause

  5. mountiny commented on Apr 26, 2024

    @mountiny
    Contributor

    I am looking if reverting #39229 will fix this

  6. mountiny commented on Apr 26, 2024

    @mountiny
    Contributor

    Making a revert here #41087

  7. grgia commented on Apr 26, 2024

    @grgia
    Contributor
  8. self-assigned this
    on Apr 26, 2024
  9. mountiny commented on Apr 26, 2024

    @mountiny
    Contributor

    This was not fully fixed with the revert, however, after refresh I have got the correct avatar there.

    Screen.Recording.2024-04-26.at.14.00.48.mp4

    @Kicu would you be able to include this flow in your testing steps for the second PR?

  10. mountiny commented on Apr 26, 2024

    @mountiny
    Contributor

    Can you please comment on this issue so I can assign you and @grgia so you can then address this avatar logic, please? Thanks!

  11. 41 remaining items

  12. added
    ReviewingHas a PR in review
    and removed on May 8, 2024
  13. melvin-bot commented on May 29, 2024

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  14. Kicu commented on May 29, 2024

    @Kicu
    Contributor

    FYI a PR that implements similar functionality that the original PR was merged. If by any chance the bug would come back please ping me. But I believe it should be fixed.

  15. changed the title [-][HOLD for payment 2024-05-06] [HOLD for payment 2024-05-03] Quick action - Fallback avatar is displayed on quick action after user avatar loads[/-] [+][HOLD for payment 2024-06-06] [HOLD for payment 2024-05-06] [HOLD for payment 2024-05-03] Quick action - Fallback avatar is displayed on quick action after user avatar loads[/+] on May 30, 2024
  16. melvin-bot commented on May 30, 2024

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  17. melvin-bot commented on May 30, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.77-11 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-06-06. 🎊

    For reference, here are some details about the assignees on this issue:

    • @Kicu does not require payment (Contractor)
  18. melvin-bot commented on May 30, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@mountiny] The PR that introduced the bug has been identified. Link to the PR:
    • [@mountiny] 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:
    • [@mountiny] A discussion in #expensify-bugs 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:
    • [@Kicu] Determine if we should create a regression test for this bug.
    • [@Kicu] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@Christinadobrzyn] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions