Skip to content

Chat with task/GBR not visible after switching Priority Mode back to Most Recent #64540

Closed

Description

@mitarachim

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.1.69-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: #64076
Email or phone of affected tester (no customers): qaooxx+199@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows / Chrome
App Component: Other

Action Performed:

  1. Create a fresh account
  2. Start a chat with a random user and send a message
  3. Go back to the LHN and confirm the chat appears at the top
  4. Long press / right-click on the Concierge chat and select "Pin"
  5. Confirm the Concierge chat moves to the top of the list
  6. Start another chat
  7. Create a task in that chat and assign it to yourself
  8. Confirm the chat appears in 1st or 2nd position in the LHN (sorted alphabetically with Concierge)
  9. Go to Account → Preferences
  10. Change the Priority Mode to Focus
  11. Return to the LHN and confirm only the pinned chat and the task/GBR chat are visible
  12. Go back to Account → Preferences
  13. Change the Priority Mode to Most Recent
  14. Return to the LHN

Expected Result:

All three chats (random user, pinned Concierge, and task/GBR chat) are visible in the LHN.

Actual Result:

Only two chats are visible in the LHN — the chat with the task/GBR is missing.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6864276_1750312133391.video_45.mp4

View all open jobs on GitHub

Activity

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

    @melvin-bot

    Triggered auto assignment to @joekaufmanexpensify (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. joekaufmanexpensify commented on Jun 19, 2025

    @joekaufmanexpensify
    Contributor

    Reproduced on android mWeb.

    2025-06-19_11-41-07.mp4
  4. joekaufmanexpensify commented on Jun 19, 2025

    @joekaufmanexpensify
    Contributor

    Works fine for me on chrome web though.

  5. joekaufmanexpensify commented on Jun 19, 2025

    @joekaufmanexpensify
    Contributor

    cc @adhorodyski @mountiny @brunovjk as seems related to this PR that's on staging

  6. mountiny commented on Jun 19, 2025

    @mountiny
    Contributor

    @joekaufmanexpensify making abuild of the revert #64599 could you please test it on that adhoc build if its repro for you same as in staging or if its fixed?

  7. joekaufmanexpensify commented on Jun 19, 2025

    @joekaufmanexpensify
    Contributor

    Yep! Will do.

  8. mountiny commented on Jun 19, 2025

    @mountiny
    Contributor

    @brunovjk Can you please test this on staging and the revert PR? Was this fixed for you in the PR?

  9. 4 remaining items

  10. adhorodyski commented on Jun 23, 2025

    @adhorodyski
    Contributor

    Any way I can help here?

  11. joekaufmanexpensify commented on Jun 23, 2025

    @joekaufmanexpensify
    Contributor

    I'm thinking we're going to tackle this and the other bug in a follow up PR. Is that right @mountiny @brunovjk

  12. mountiny commented on Jun 23, 2025

    @mountiny
    Contributor

    Ype in the other one, commented there

  13. joekaufmanexpensify commented on Jun 24, 2025

    @joekaufmanexpensify
    Contributor

    TY!

  14. joekaufmanexpensify commented on Jun 26, 2025

    @joekaufmanexpensify
    Contributor

    @adhorodyski are you planning to include this one in your PR from the other issue?

  15. adhorodyski commented on Jun 26, 2025

    @adhorodyski
    Contributor

    Separately, I couldn't reproduce the other one for the whole day today (see my last comment, asked for a retest).
    I'll look into this one first thing tomorrow morning.

  16. adhorodyski commented on Jun 27, 2025

    @adhorodyski
    Contributor

    I was able to reproduce this on Web (Mac) with @kubabutkiewicz, here are the takeaways:

    It's a BE issue to me because FE renders correctly when it has this report available in Onyx.
    It's not reproducible when we're offline.

    1. Changing priority mode calls the OpenApp command (should it?) which runs setCollection (was merge back in the days but setCollection means better perf) on reports_ that is missing this report ...972 (that should have a GBR).

    Image

    1. When we navigate to this missing report (...972) from Reports -> Chats (via a snapshot), OpenReport gets called and merges back this report. From then on, it's visible in LHN just because it's back in our Onyx state.

    Image


    To fix this, we need to return it with OpenApp.

  17. joekaufmanexpensify commented on Jun 27, 2025

    @joekaufmanexpensify
    Contributor

    Thanks for the investigation! I am personally not super passionate about fixing this right now, given the reproduction behavior is so niche. WDYT @mountiny ? If you want to fix it though, totally fine with me too.

  18. mountiny commented on Jun 30, 2025

    @mountiny
    Contributor

    I agree, I think we need to take a more holistic approach to the GBR/ RBR stuff to fix these properly, I would like to poke that idea around in quality but dont think its worth the time now to spend on this individual issue.

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

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions