Warnings: componentWillReceiveProps in strict mode, Legacy context API, findDOMNode is deprecated

[bladey]

This issue is a round-up of multiple past issues documenting the same bug. Feel free to check out the linked issues below for more information. This issue is the source of truth going forward to investigate the issue, report findings, and implement a bug fix.

Issue:

Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://fb.me/react-unsafe-component-lifecycles for details.

Warning: Legacy context API has been detected within a strict-mode tree.

The old API will be supported in all 16.x releases, but applications using it should migrate to the new version.

Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of NodeResolver which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://fb.me/react-strict-mode-find-node

Issues:

#3751
#3720
#3915
#3745
#4068
#3703

If anyone would like to share any further information, please do so.

[giangr21]

Same issue here

[Sine99]

same issue

[manvydasu]

So basically someone would have to create a PR and replace legacy component lifecycle methods with newer version: https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html#migrating-from-legacy-lifecycles

However, looking at usages and code inside of UNSAFE_componentWillReceiveProps , it might not be so straightforward.

[stak99]

same issue