Repository navigation
Thread - App flickers & returns to main chat when leaving and reentering thread #45834
Description
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.0.10-2
Reproducible in staging?: y
Reproducible in production?: no new feature
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):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:
- Go to staging.new.expensify.com
- Go to workspace chat.
- Send a message.
- Open the message in thread > Send a message in thread.
- Leave the thread via thread header.
- Click on the thread subtitle to return to main chat.
- Open the thread again from the main chat.
- Note that app auto returns to main chat.
DM issue
- Go to staging.new.expensify.com
- Go to DM.
- Send a message.
- Open the message in thread > Send a message in thread.
- Leave the thread via thread header.
- Click on the thread subtitle to return to main chat.
- Open the thread again from the main chat.
- Note that thread flickers briefly.
Expected Result:
No flicker issue and app will remain on the same thread when leaving and reentering thread.
Actual Result:
- In workspace chat, thread flickers and auto returns to main chat after leaving and reentering thread.
- In DM, thread flickers briefly and remains on the same thread when leaving and reentering thread in DM.
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
Bug6547839_1721477323941.20240720_200016.mp4
Issue Owner
Current Issue Owner: @chiragsalianMetadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
melvin-bot commentedon Jul 20, 2024
Triggered auto assignment to @trjExpensify (
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.melvin-bot commentedon Jul 20, 2024
Triggered auto assignment to @srikarparsi (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jul 20, 2024
👋 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:
tsa321 commentedon Jul 21, 2024
This seems related to my PR regarding loading the skeleton of the report screen (I believe only related to report action list). However, the loading is also displayed for the composer and header of the report, which are different components from the the report action list. I will investigate further.
tsa321 commentedon Jul 21, 2024
It seems like this is a backend issue. When user leaves the thread and returns to the parent report, and then goes back to the thread again,
GetMissingOnyxMessagessets thereportandreport_actionsto null.34 remaining items
muttmuure commentedon Aug 6, 2024
https://stackoverflowteams.com/c/expensify/questions/19512
chiragsalian commentedon Aug 21, 2024
oh whoops i thought this was an external issue. I'll try to catch up on this when i get the chance.
muttmuure commentedon Aug 27, 2024
Oh, I think I misunderstood what this issue was, I'm going to add it to UX reliability
chiragsalian commentedon Sep 3, 2024
Okay i finally got some free time to check this out today. I tested on main and staging and I'm unable to reproduce the issue.
After i leave the thread, when i click into the thread again i only see an OpenReport network request. I do not see a GetMissingOnyxMessages request. Maybe this was resolved but a change in flow elsewhere.
Can someone else retest and confirm if this issue still persists? @m-natarajan @tsa321 @muttmuure. If not we can close out this issue.
tsa321 commentedon Sep 4, 2024
I think this issue has been fixed. I am unable to reproduce it in staging.
muttmuure commentedon Sep 5, 2024
OK seems to be fixed on staging for me
muttmuure commentedon Sep 5, 2024
Going to close
muttmuure commentedon Sep 5, 2024
Thanks!