-
Notifications
You must be signed in to change notification settings - Fork 70
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
Error: Tyring set data after component(Container(ChartData)) has unmounted. #152
Comments
Also getting this when using a controlled component and someone types quickly. |
Not sure about v2 but if you look at the code in v1 it actually sets data in |
Anyone happen to figure this out? Following the recommended setup we see this after routing (with react router) and it causes the app to completely break. |
Actually we found this was caused by the mapper function for redux not returning the result of subscribe (which is a function that unsubscribes from the store). |
Any solution to this? We are also seeing this issue. We have a sidebar that has our komposer container inside of it. When we close the sidebar, the container seems to re-render as it's closing. In our container, we fetch our data via a If I provide static data, instead of doing the Meteor call, then everything is fine. |
I am also running into this issue. Here is some pseudo code.
I am making a network call in doSomething. If I navigate away and the component becomes unmounted, I would be expecting cancelDoSomething to be called, but it appears that it is not. (I have verified this via logging). Instead I am getting the following error.
The solution for me at the moment, is to just catch the error that was thrown. Which isn't great. |
I keep seeing this error, for a dataLoader function which is very fast.
Is there a chance the dataLoader is trying to set the data into the component before it is actually mounted?
The text was updated successfully, but these errors were encountered: