RippledComponent warning: Can't call setState (or forceUpdate) on an unmounted component

When Button is unmounted, React will produce warning as bellow:

Warning: Can't call setState (or forceUpdate) on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
    in RippledComponent (created by App)

Here is minimal test case that would produce warning when button is clicked: https://codesandbox.io/s/9zw5v67kn4

[bmihelac]

I think that this is broader issue that would repeat with other components as well in similar situations. From what I understand this is what happens:

1. When Interacting with material components, they initiate changes to be made by adapter like updating css classes, attributes and styles of component underneath HTML elements as well as requesting value of some attributes and properties. For animation this changes can take some time.

2. If same interaction makes React component to be unmounted before foundation is over with what it is doing, various warnings/errors could be produced as adapter tries to set state and update/read underneath HTML elements class, styles, attributes.

Adapter methods that manipulate state or update/read underneath HTML elements should probably be shortcircuted when component is unmounted. Maybe it would be great to have this extracted to some util functions so every react component does not have to do same checks over and over again.

[moog16]

@lucasecdb I’ve taken a look at your PR, but I’m suspecting that it is an issue across the board. Similar to what @bmihelac is saying, so I want to investigate before reaching any conclusions. I just haven’t had the time (not ignoring this issue).