[Android] Node has not been attached to a view in PropsAnimatedNode.updateView #12893
Description
Description
Seems like there are some rare cases will cause the following error:
Fatal Exception: java.lang.IllegalStateException: Node has not been attached to a view
at com.facebook.react.animated.PropsAnimatedNode.updateView(PropsAnimatedNode.java:49)
at com.facebook.react.animated.NativeAnimatedNodesManager.runUpdates(NativeAnimatedNodesManager.java:453)
at com.facebook.react.animated.NativeAnimatedModule$1.doFrameGuarded(NativeAnimatedModule.java:117)
at com.facebook.react.uimanager.GuardedChoreographerFrameCallback.doFrame(GuardedChoreographerFrameCallback.java:32)
at com.facebook.react.uimanager.ReactChoreographer$ReactChoreographerDispatcher.doFrame(ReactChoreographer.java:131)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:824)
at android.view.Choreographer.doCallbacks(Choreographer.java:605)
at android.view.Choreographer.doFrame(Choreographer.java:574)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:812)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:6918)
at java.lang.reflect.Method.invoke(Method.java)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1404)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1199)
Additional Information
- React Native version: 0.42
- Platform: Android
- Operating System: MacOS
- Dev tools: Android Studio 2.3
Reacted by Bhaskar Murthy, HyperSimon, Thijs Wiefferink, Jose Gonzalez, Cesar Augusto, Jakob Hilden, Danny Cochran, Arman Dezfuli-Arjomandi, Sid Jain, Christoph Jerolimov and 9 more
Activity
HyperSimon commentedon Apr 18, 2017
Same here
jose920405 commentedon Apr 25, 2017
+1
LucasdeCastro commentedon May 12, 2017
+1
jhilden commentedon May 15, 2017
We are seeing the same issue in our production RN app. We are on version
0.42.3and, as already stated, it only happens on Android.Any pointers in which direction to look, would be extremely appreciated.
Here is our stacktrace, but it is pretty much identical to the one @rayshih posted.
jkomyno commentedon May 26, 2017
This has been useful to me:
react-navigation/react-navigation#438
Blapi commentedon Jun 1, 2017
Had this issue when trying to access to this.props in a constructor (yeah I've been dumb..), if that can help..
tmaly1980 commentedon Jun 19, 2017
I have this issue on IOS too
maraujop commentedon Jun 30, 2017
I've seen this happen when I rename a method in a component but I forget to update
this.method = this.method.bind(this)in the constructor and pass this method as a property to a child component.xvjianzhe commentedon Jul 12, 2017
+1
hramos commentedon Sep 21, 2017
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.
8of commentedon Oct 2, 2017
Problem still persist on
0.47.2.App sometimes crashes on the line 489:
https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/uimanager/UIImplementation.java#L489
DeividVeloso commentedon Nov 2, 2017
Problem still persist on ^0.48.4",
anAngryAnt commentedon Dec 15, 2017
Problem still persist on 0.48.4
hushicai commentedon Dec 27, 2017
The same issue in 0.47.2
christoph-jerolimov commentedon Jan 2, 2018
FYI: This commit 2b4ff6e#diff-ed80d5990dea7c0f1947e73bb23569ddL49 is part of the react-native release 0.51.0 and changed the assertion / exception / behaviour.
With this version this exception should not happen anymore. I hadn't time to verify this with our app, which has many of these crashes, too.
skizzo commentedon Mar 12, 2018
@jerolimov Did updating to 0.51 solve your issues?
React sync for revisions c0fe8d6...ae14317
EstebanMarin commentedon Jun 18, 2018
You should check any type of error, mainly a
TypeorReferenceerror. This is a silent error, it does not appear inReact Packager, therefore, check any hints in your console. In my experience, when I have this is a consequense of another error, therefore, it is not able to mount the node.React sync for revisions c0fe8d6...ae14317