ReactNativeFiberHostComponent: 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.

[Preeternal]

Describe the bug
I got an warning:
ReactNativeFiberHostComponent: 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.

[slavagoreev]

@Preeternal please, see this response. Reanimated should be of v1.
yarn add react-native-reanimated@1

#244 (comment)

[hraschan]

Is their a way to use Reanimated version 2 without the above mentioned warning?

[freezen82]

i have same issue with expo sdk 41. it updated Reanimated v2 and not downgradable.

[dkoodev]

Will this package support using reanimated v2 in the future?

[alburdette619]

Also interested in using with reanimated v2, we are using it and hermes on both platforms.

[NxsHbb]

@Preeternal please, see this response. Reanimated should be of v1.
yarn add react-native-reanimated@1

#244 (comment)

I am using expo SDK 42 and this solved my problem. Thanks....

[Makatun]

I am using expo SDK 42 too but still see the problem

[salamisodikiolawale]

Hello, I have the same and my project works with expo, I tried the different methods but I had errors 500. and so I came back to version 2 of reanimed, how can I set the warning with expo. it is urgent please

[slavagoreev]

Hello, I have the same and my project works with expo, I tried the different methods but I had errors 500. and so I came back to version 2 of reanimed, how can I set the warning with expo. it is urgent please

The only way how you may handle this is to ignore this error.

// App.tsx
import { LogBox } from 'react-native';

LogBox.ignoreLogs([
  'ReactNativeFiberHostComponent: 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.',
]);

[slavagoreev]

Exactly the same fix were added to the library in https://github.com/computerjazz/react-native-draggable-flatlist/pull/278/files

[salamisodikiolawale]

How do I go about it?
i begining to react-native, can you give me directive for solve problems.

[slavagoreev]

How do I go about it?
i begining to react-native, can you give me directive for solve problems.

1. Use reanimated v2
2. Add the code I provided above in your App.jsx
3. It will suspend the warning and the rest will work just fine

[salamisodikiolawale]

#277 (comment)

Yessss, Thank you so much, it works.

[jamesxabregas]

I hope everyone here realizes that hiding a deprecation warning isn't a real solution to this problem, it's just a convenient way to forget it exists until one day React Native does deprecate it and this library is broken...

[itsramiel]

is there a solution for this, or will this package get updated? It is a really useful one for react native developers

[maxfahl]

I'm really hoping for some issues to get resolved. This is an extremely helpful project, unfortunately it's open source, so we can't count on frequent updates.

[itsramiel]

I believe it is being worked on. I install the beta version using "npm install react-native-draggable-flatlist@3.0.0-beta.11". The error is fixed and seem to be working fine, but i guess it is still being tested

[maxfahl]

That's great news. Did not check for other branches. Seems there has been some activity lately, awesome!

I'm really thankful for the work you're doing here @computerjazz, my application would be kind of a mess without this package.

[NxsHbb]

Exactly the same fix were added to the library in https://github.com/computerjazz/react-native-draggable-flatlist/pull/278/files

Thanks. updating react-native-draggable-flatlist solved my issue.