-
Notifications
You must be signed in to change notification settings - Fork 71
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
UIFreeze: Tried to remove a willPop callback from a route that is not currently in the tree. #46
Comments
@anburocky3 I can't reproduce it. Can you show your code and environment or provide an example? |
Sorry, i have it in my project, is there any way, i can contact you via discord, to share the credentials? |
I'm facing the same issue either. In my case, it's because I called a Navigator Pop. so the BuildContext are not in the Stack anymore. So I tricked it with Future.delayed before navigator pop called. |
Facing the same issue. |
You can try my solution above. It's not elegant solution, because delayed pretty much expensive task, but it works. I think the problem is, there is a async delay beetwen disposing Flash dan the Navigator.pop that makes current BuildContext already disposed and throw this error. |
you need create the another completer for handle race condition.
|
I noticed that, after i call this:
It is displaying properly on the UI, but on the log, i can see this trace. And during that, my UI is freezen, i have to restart my app to use my app. Why is that?
The text was updated successfully, but these errors were encountered: