Calling `getNode()` on the ref of an Animated component is no longer necessary
See original GitHub issueGetting the following warning on RN 0.62.
FlatList: Calling
getNode()
on the ref of an Animated component is no longer necessary. You can now directly use the ref instead. This method will be removed in a future release.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Calling getNode() on the ref of an Animated component is no ...
I got an warning: ReactNativeFiberHostComponent: Calling getNode() on the ref of an Animated component is no longer necessary. You can now directly use...
Read more >Upgraded to React Native 0.62.0 Getting Warning Sign
The warning begins like this: Calling getNode() on the ref of an Animated component is no longer necessary. You can now directly use...
Read more >Upgraded to React Native 0.62.0 Getting Warning ... - iTecNote
ReactNativeFiberHostComponent: Calling `getNode()` on the ref of an Animated component is no longer necessary. You can now directly use the ref instead. This ......
Read more >Calling `getNode()` on the ref of an Animated component is no ...
[Solved]-Calling `getNode()` on the ref of an Animated component is no longer necessary. You can now directly use the ref instead-React Native.
Read more >Calling getNode() on the ref of an Animated component is no ...
ReactNativeFiberHostComponent: Calling getNode() on the ref of an Animated component is no longer necessary. You can now directly use the ...
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 Free
Top 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
Oh you’re totally right, this is a react-navigation issue. Thanks for your help and for the great package!
If you are not calling
getNode
, then it is not related to rnchv.getNode
is not called from the module.