-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$500] [MEDIUM] LHN - Green dot(IOU) disappears from WS conversation in LHN when going offline-online #33544
Comments
Job added to Upwork: https://www.upwork.com/jobs/~019c2e500b47b7def2 |
Triggered auto assignment to @Christinadobrzyn ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov ( |
👋 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:
|
Triggered auto assignment to @aldo-expensify ( |
First of all, this is not a deploy blocker – it's happening in prod as well: We're potentially facing the out-of-order Onyx updates again: First comes the Second comes the This particular issue can be fixed by making sure the cc: @Julesssss for the out-of-order updates |
📣 @aim-salam! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
Current assignee @alitoshmatov is eligible for the Internal assigner, not assigning anyone new. |
Hi! I'm Bartosz from Software Mansion, I was working on this issue yesterday (I wanted to run a few more tests today) and I think that it may have been fixed with navigation rework. Following these steps here's the result: lhn-test.mp4 |
oh, nice! thanks for taking a look @BartoszGrajdek |
👋 @BartoszGrajdek where you able to run more tests? |
Oh, I took it as if you didn't need any more help, so I just shared what I have found out. I tested out several scenarios with going online/offline and it really looks like it got fixed. I can investigate what might have fixed this problem if you want to - just let me know 😄 |
No need @BartoszGrajdek , thank you again. If we can't reproduce, we can just close this. |
Issue is still reproducible on the latest build 1.4.40-1 Recording.1331.mp4 |
Well, that's strange. I tested it by trying both steps found here and here. I also tried it on multiple browsers just to be sure and I still couldn't reproduce the problem. Maybe I'm missing something, or this is some edge case and we still haven't figured out all the necessary steps. I'm attaching a video of how it behaves for me (build 1.4.40-4) @lanitochka17 let me know if there's anything I have done incorrectly there. |
For some reason I'm not being able to reproduce in Screen.Recording.2024-02-13.at.11.14.10.AM.mov |
From looking at |
Reproduced in dev, the key is that the account has to have the beta |
I have a fix here https://github.com/Expensify/Auth/pull/9929, I just need to add the tests and I'll make it ready for review |
Yay! Exciting @aldo-expensify! |
PR was deployed |
Tested and now it is working: Screen.Recording.2024-02-14.at.12.42.17.PM.movIn the video we can see that the policyExpenseChat (reportID: 2130476157825373) comes with |
hey @aldo-expensify or @alitoshmatov do we need to pay out anyone for this? |
@Christinadobrzyn not as far as I know, the backend PR wasn't reviewed by C+ |
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.16-3
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
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:
excludedFromReliableUpdates
.Expected Result:
The IOU green dot must be present in the LHN in any mode of operation until the IOU request is paid or an IOU error occurs.
Actual Result:
The green dot IOU disappears from the LHN if the user goes offline and comes back online.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6324826_1703328627225.Recording__981.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: