Warning: componentWillMount is deprecated
See original GitHub issueIssue
I’m receiving a warning about componentWillMount
is deprecated.
Warning: componentWillMount is deprecated and will be removed in the next major version. Use componentDidMount instead. As a temporary workaround, you can rename to UNSAFE_componentWillMount.
Please update the following components: AnimatedComponent
Learn more about this warning here:
https://fb.me/react-async-component-lifecycle-hooks
Versions:
“react”: “16.8.6”, “react-native”: “0.60.4”, “react-native-reanimated”: “^1.1.0”,
Issue Analytics
- State:
- Created 4 years ago
- Reactions:35
- Comments:14
Top Results From Across the Web
componentWillMount is deprecated and will be removed in ...
componentDidMount isn't deprecated and is definitely still safe to use, so there's no need to add UNSAFE_ to that method.
Read more >React: componentWillMount to be deprecated!
Starting with React v16.3.0, new versions of these methods categorised as unsafe have be created, and the legacy versions will come with deprecation...
Read more >Warning: componentWillMount has been Renamed, and is ...
Learn what causes "Warning: componentWillMount has been renamed, and is not recommended for use."
Read more >React Native Solve Warning componentwillmount is ...
Warning: componentWillMount is deprecated and will be removed in the next major version. Use componentDidMount instead.
Read more >Warning componentwillmount is Deprecated and will be ...
Warning componentwillmount is Deprecated and will be Removed in the Next Major Version in React Native Solved.The above lifecycle methods ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The fix has been pushed to master, but isn’t on npm yet. I would rather not blanket ignore cpm deprecation warnings, in-case any others come along that could be missed.
Changes has been merged in 1.3.0. You can close this issue.