Skip to content

[HOLD for payment 2024-05-06] [$250] Quick action - Group chat name and avatar does not update unless the page is refreshed #40536

Closed

Description

@izarutskaya

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.63-5
Reproducible in staging?: Y
Reproducible in production?: No, new feature
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to FAB > Start chat.
  3. Create a group chat.
  4. Split expense in the group chat.
  5. Click on the chat header.
  6. Go to Settings > Name.
  7. Change the group chat name.
  8. Also change the group chat avatar.
  9. Click FAB.
  10. Hover over the group chat avatar.

Expected Result:

The group chat under Quick action in FAB will update to show the latest avatar and name.

Actual Result:

The group chat under Quick action in FAB does not show the latest avatar and name (in the tooltip) unless the page is refreshed.

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

Bug6454364_1713485468784.20240419_080236.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0158c8e7015a29644e
  • Upwork Job ID: 1783268294358458368
  • Last Price Increase: 2024-04-24
  • Automatic offers:
    • shubham1206agra | Reviewer | 0
    • bernhardoj | Contributor | 0

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 19, 2024
  2. melvin-bot commented on Apr 19, 2024

    @melvin-bot

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

  3. melvin-bot commented on Apr 19, 2024

    @melvin-bot

    Triggered auto assignment to @isabelastisser (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.

  4. github-actions commented on Apr 19, 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.
  5. izarutskaya commented on Apr 19, 2024

    @izarutskaya
    Author

    @isabelastisser 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.

  6. izarutskaya commented on Apr 19, 2024

    @izarutskaya
    Author

    We think this issue might be related to the #collect project.

  7. ZhenjaHorbach commented on Apr 19, 2024

    @ZhenjaHorbach
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Quick action - Group chat name and avatar does not update unless the page is refreshed

    What is the root cause of that problem?

    The main problem with issue is that we can' get actual ActionReport because we use useMemo
    As a result, we are unable to update the data

    What changes do you think we should make in order to solve the problem?

    To fix this issue we can refactor this component and use allReports directly to always have actual information from report

    const quickActionReport: OnyxEntry<OnyxTypes.Report> = useMemo(
        () => (quickAction ? allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${quickAction.chatReportID}`] : null),
        [allReports, quickAction],
    );
    

    const quickActionReport: OnyxEntry<OnyxTypes.Report> = useMemo(() => (quickAction ? ReportUtils.getReport(quickAction.chatReportID) : null), [quickAction]);

    For optimisation we can use selector just like we do for allPolicies on this screen

    const policySelector = (policy: OnyxEntry<OnyxTypes.Policy>): PolicySelector =>
    (policy && {
    type: policy.type,
    role: policy.role,
    isPolicyExpenseChatEnabled: policy.isPolicyExpenseChatEnabled,
    pendingAction: policy.pendingAction,
    avatar: policy.avatar,
    name: policy.name,
    }) as PolicySelector;

    What alternative solutions did you explore? (Optional)

    As alternative we don't have to use useMemo

  8. 35 remaining items

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Apr 29, 2024
  10. changed the title [-][$250] Quick action - Group chat name and avatar does not update unless the page is refreshed[/-] [+][HOLD for payment 2024-05-06] [$250] Quick action - Group chat name and avatar does not update unless the page is refreshed[/+] on Apr 29, 2024
  11. melvin-bot commented on Apr 29, 2024

    @melvin-bot

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

  12. melvin-bot commented on Apr 29, 2024

    @melvin-bot

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

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

  13. melvin-bot commented on Apr 29, 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:

    • [@shubham1206agra] The PR that introduced the bug has been identified. Link to the PR:
    • [@shubham1206agra] 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:
    • [@shubham1206agra] 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:
    • [@shubham1206agra] Determine if we should create a regression test for this bug.
    • [@shubham1206agra] 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.
    • [@isabelastisser] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  14. isabelastisser commented on May 8, 2024

    @isabelastisser
    Contributor

    The payments were processed in Upwork.

    @shubham1206agra, please complete the BZ list above before I can close the issue. Thanks!

  15. shubham1206agra commented on May 9, 2024

    @shubham1206agra
    Contributor

    The payments were processed in Upwork.

    @isabelastisser Can you check this again? Looks like my payment was not processed.

  16. shubham1206agra commented on May 9, 2024

    @shubham1206agra
    Contributor

    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:

  17. isabelastisser commented on May 14, 2024

    @isabelastisser
    Contributor

    Confirming that the payments were processed in Upwork on May 8:

    image image
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.EngineeringExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions