-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
newDot becomes unresponsive randomly when switching chats #8201
Comments
Triggered auto assignment to @nkuoch ( |
cc @tgolen as this is related to your |
Hm, it sounds though like it works after a couple of seconds? Maybe that's more related to the performance stuff that Carlos is doing. I'm sure both projects will probably impact this behavior. I'm going to leave it unassigned but open so that we don't totally forget about this, but for right now, I'm not going to address it directly. |
I think this is a probable duplicate of #7950. it's a 🐰 🕳️ that we are fairly close to solving so I'm going to assign myself here and see if my changes will resolve this issue. |
@marcaaron so should we close this, given the other issue is trying to fix the same thing? |
Confirmed it's a dupe after testing. My PR should fix this (and maybe other things). |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
NewDot should not lag or crash or become unresponsive
Actual Result:
NewDot becomes unresponsive randomly when switching chats
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.42-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @iwiznia
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1647462425056679
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: