Skip to content

[Due for payment 2025-08-22] Chat - Both avatars are still shown for User A after he deleted all created expenses #67962

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: 9.1.89-11
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: #65740
Issue reported by: Applause - Internal Team

Action Performed:

  1. Sign in to ND with two accounts - User A and User B
  2. As user A create 2 expenses to user B - verify you see only user's A avatar on the report preview, report header, in the report details, in the Reports/Chats and report LHN
  3. Create 2 expenses as user B to user A - verify you see both users avatars
  4. Delete every expense that user A has created - verify you see only user's B avatar.

Expected Result:

After User A deleted all created expenses, only User B's avatar is shown

Actual Result:

After User A deleted all created expenses, both avatars are still shown for this user on the report preview, report header, in the report details, in the Reports/Chats and report LHN until the app is refreshed. For User B only his avatar is shown correctly

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6908690_1754420419550.Both_avatars.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 5, 2025
  2. melvin-bot commented on Aug 5, 2025

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (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. grgia commented on Aug 6, 2025

    @grgia
    Contributor

    Not a blocker

  4. JakubKorytko commented on Aug 8, 2025

    @JakubKorytko
    Member

    Found a fix, will be resolved as a part of #68120

    CBAASSFUAAHDACE.mov
  5. added
    ReviewingHas a PR in review
    and removed on Aug 8, 2025
  6. melvin-bot commented on Aug 12, 2025

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

  7. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Aug 15, 2025
  8. changed the title [-]Chat - Both avatars are still shown for User A after he deleted all created expenses[/-] [+][Due for payment 2025-08-22] Chat - Both avatars are still shown for User A after he deleted all created expenses[/+] on Aug 15, 2025
  9. melvin-bot commented on Aug 15, 2025

    @melvin-bot

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

  10. melvin-bot commented on Aug 15, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.94-4 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 2025-08-22. 🎊

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

  11. melvin-bot commented on Aug 15, 2025

    @melvin-bot

    @grgia @mallenexpensify @JakubKorytko 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]

  12. mallenexpensify commented on Aug 22, 2025

    @mallenexpensify
    Contributor

    @c3024 if you're due payment here for this PR (which as issued linked to it in the OP), please comment here

  13. melvin-bot commented on Aug 22, 2025

    @melvin-bot

    Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

  14. c3024 commented on Aug 23, 2025

    @c3024
    Contributor

    @mallenexpensify , yes, I was not assigned to any of the issues mentioned in the PR.

  15. mallenexpensify commented on Aug 25, 2025

    @mallenexpensify
    Contributor

    Thanks @c3024 . Think we can close this then. Please comment or reopen if ya disagree.

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.DailyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions