-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2024-12-20] Investigate useOnyx infinite loading state related to the Connection Manager #52640
Comments
Hi @gijoe0295 Could you confirm for me if you are still being able to reproduce this loading state issue? I'm having difficulties to reproduce it. If you are able could you give me the detailed test steps again? Thanks |
@ishpaul777 maybe you can help me here with reproducing the problem from your side? We need to remove |
I'll check a confirm in few hours |
Tried multiple times, no luck reproducing this is resolved mysteriously Screen.Recording.2024-12-01.at.10.10.10.PM.mov |
@ishpaul777 Should we close this issue then? I asked @kubabutkiewicz to help me with testing and he wasn't able to reproduce it too. |
However we can try removing |
yes i think that should be a good next step forward 👍 |
Update: Created a WIP Draft PR. Will proceed with testing soon. |
@ishpaul777 PR open to review! |
Triggered auto assignment to @neil-marcellini, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
PR was merged! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.75-6 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-12-20. 🎊 |
This issue was first noticed here -> #49509.
I recently implemented a fix in Onyx to solve the infinite loading states after a Onyx.clear() operation, but in this case they are happening without the clear operation, so we must investigate it again.
Report of the problem: #49509 (comment)
Reproducible steps: #49509 (comment)
My initial investigations: #49509 (comment)
The text was updated successfully, but these errors were encountered: