-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning : Calling 'getNode()' on the ref an Animated Component is no longer necessary. #672
Comments
having same issue react-native v 0.61 occurs implementing nested navigation. |
@lumberman Give #673 a try :) |
same problem but im using the 'react-native-image-slider-box' which is using the carousel. |
i fixed ,in this way, const AnimatedFlatList = FlatList ? Animated.createAnimatedComponent(FlatList) : null; to after find function _getWrappedRef then save it . |
Thankyou so much, It helped. |
Hi, any updates on when this will be release ? |
I am looking for the release too :) |
waiting for the release |
waiting for release too |
waiting for release too ;) |
+1 waiting for the release |
waiting for release too! |
1 similar comment
waiting for release too! |
¿Cuando se arreglara ese problema en el repositorio? |
I am looking for the release too |
+1 |
1 similar comment
+1 |
Would love to see this 'acclaimed' release |
Waiting.... |
Yes waiting... |
Waiting |
Yes waiting... |
Waiting for this release too |
waiting |
waiting too.. |
waiting |
waiting .. |
waiting |
I don't know how all you guys commenting "waiting" here think this will solve the problem. maybe stop polluting the thread with useless comments, and a 👍 should be enough. |
Why the PR is not merged yet? It is really annoying working with those warnings |
Probably because it is really complicated to detect the RN package Version the right way. |
Thanks, This is also working with react-native-image-slider-box.... Thanks for help |
…uecomment-611512460
Chill out and wait a little guys. It’s been 10 days not 10 months since the PR was filed and theres an ongoing discussion about the implementation. Either contribute or be patient. Open source doesn’t work by stressing contributors out but by contributing and being grateful for the contributions of others. |
Well, the main issue is that the suggested implementation is not backward compatible, meaning the plugin will break on every version of React Native but This is a no-go for us, so unless someone comes up with a backward-compatible solution, we just can't merge this. (Take a look at #673 if you want to follow the discussion.) Basically, what we need is a surefire way to identify whether What we've tried so far:
Running out of ideas here, so if you have a reliable solution, don't be shy and share it with us :-) |
Ok, looks like this is going to be fixed pretty soon! |
Fixed in versions |
Hi! I reached out this thread when I faced this 'getNode()' warning and I was using
I am running on react-native v 0.62.2 |
In updated version I changed this
to this:
as mentioned by @binar1 above I think any how this change did not get pushed into the update. |
In the 3.9.1 release, the error did not disappear, so I used the @HarshitMadhav advice and with the help of patch-package fixed the problem so as not to wait for a new release. Thanks @HarshitMadhav ! |
I can confirm that this warning has not been resolved |
Tested this on react-native 0.63.4 and react-native-snap-carousel 3.9.1 and it is still happening |
still happening. 0.63.3 and react-native-snap-carousel 3.9.1 |
Well now its been more than 10 months and problem still exists... |
this will help!!! |
Is this a bug report, a feature request, or a question?
Question
Have you followed the required steps before opening a bug report?
(Check the step you've followed - put an
x
character between the square brackets ([]
).)Have you made sure that it wasn't a React Native bug?
It is a warning regarding deprecation of the method
getNode()
.Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
(Write your answer here and specify the iOS/Android versions on which you've been able to reproduce the issue.)
Is the bug reproductible in a production environment (not a debug one)?
Yes.
Environment
React native: 0.62.0
react-native-snap-carousel: 3.8.4
Target Platform:
Android (9.0)
iOS (13.3)
Expected Behavior
No warning should be raised. Upgrade is needed.
Actual Behavior
Raise of a warning.
Reproducible Demo
(Paste the link to a Snack example in which the issue can be reproduced. Please follow the guidelines for providing a Minimal, Complete, and Verifiable example.)
Steps to Reproduce
The text was updated successfully, but these errors were encountered: