App crashes randomly on Android 12 with JSApplicationIllegalArgumentException: Animated node with tag ### does not exists
#33375
Comments
|
I'am getting this error too! I created a repo with a simple app as example: https://github.com/jefersonvinicius/react-native-crashing-example Some extra information:
|
|
Meeting the same crash randomly at version both 0.64.2 and 0.67.3 First i think the point is |
|
Is there a solution? |
Nearly the same, but I got this error even in debug mode randomly. |
|
#33400 |
|
same here |
@coolguy001tv can you try |
|
@guptayush thanks for the reply. But it doesn't help me a lot. I tried to comment the |
I tried your example in 0.67.1 with Mi12(Xiaomi 2201123C, android 12), which still crashed in debug mode and release apk. But I can only reproduce the crash in your Listing Page in the example, I can't reproduce in Animations Page. |
|
Can somebody help? I get nearly mad... |
Yesterday i got a fool-way but not try yet to avoid the crash for a short time:
|
|
Looked at Sentry logs of my RN app on production. Here are the list of device models on which this crash is happening.
Hope this helps. For now disabling animation on these devices. All of them are on Android 12. |
|
How can I disable all the animation? I have hundreds of pages and some other dependencies... |
I am trying to do this too... |
|
Today i find out another Maybe between the two crash have some relationship.
|
|
any updates on this issue? it happens only on android 12 devices. This crash also happens java.lang.IllegalArgumentException |
|
We are also meeting those exceptions like After doing this, we find the crash happened less than before.(The log shows it indeed gets into the code before the We know the right thing should be look deeper in why parentNode/childNode is null, but we are not android developer, so we have to try to bypass those exceptions. Still waiting for help... |
|
Facing the same issue. it happens only on android 12 devices. Sentry log - https://sentry.io/share/issue/412e43bba0594b70a3e4327ecbb4199d/ Any solution or workaround? |
|
@LiuIos Maybe the title can be modified to be android 12 to be more specific. It seems that it happens only on android 12 devices according to our discussion. |
LiuIos
changed the title
|
@cortinico sorry to disturb, but can you help us to solve this bug in android 12? It bothers us a lot in such a long time and there's still no one can offer deeper help. |
|
I'm having the same problem for a few weeks now. I also confirm that it happens just on devices running Android 12... It just crashes randomly. |
|
Has anyone tried react-native@0.63.4? I found that some people said it would be OK to reduce from 64 to 63. |
I did not get this error with mi 10 pro device! I tried this sample project,but did not crashed in any page.Maybe my testing device is ok with this issue.But I fond that some people said it would be OK to reduce react-native from 64 to 63,can you try it and offer the result? |
|
what about 0.66? |
Can u post more info(like url) on this discussion? |
my device's android version is 12.It is upgrated yesterday. |
|
Hey @HessiPard it's reproducible for us on reanimated v1 or v2 |
|
I reproduced my app on an empty react-native template, took me a whole day but it's working now. |
|
@Sabbaghh Is it possible to upload this project to Github so @mikehardy could take a look? |
|
@oleksandr-dziuban Sorry, it's a private repo for a client that my company have. |
|
Don't tag me haha, I don't suffer this crash and I'm travelling. I've only been trying to set appropriate expectations since it was tagged in to the release discussion. Those expectations should be that if you are affected you've got to produce a reproduction others can run and a PR is worth more than a reproduction. Standard expectations really but somehow not widely understood 🤷 |
|
@Sabbaghh if you can reproduce it on empty RN template os please just upload this template project to public repo. Private repo is not needed for bug reproduction) |
|
This happen for my app to, the sad thing is that I could only see this issue on Google crashes report. I cannot reproduce this on debug. |
|
@AlenToma that does not move the issue forward
Share the reproduction! |
|
I am trying to reproduce the issue with no luck. I only see the crash on google crash report and hade not been able to reproduce the issue on release or otherwise on android emulator with android 12. Still trying Though, will let you know if I can reproduce the issue. |
|
Tried on Samsung devices on Samsung websites with no luck reproducing's the issue. |
|
Here is what I get on google play console. another thing is that all the reports comes from |
This comment was marked as duplicate.
This comment was marked as duplicate.
|
Any progress? |
|
@MuhammadRafeh this issue needs a clean reproduction. Do you have one to share? If not, there's no progress. If no one else posts one, there's no progress. No need to ask, you'll see someone post it here, then you can just see it |
|
facing the same issue, the app is crashing on android 12 randomaly. |
|
@mikehardy facing this issue in production Exception com.facebook.react.bridge.JSApplicationIllegalArgumentException:
at com.facebook.react.animated.NativeAnimatedNodesManager.connectAnimatedNodes (NativeAnimatedNodesManager.java)
at com.facebook.react.animated.NativeAnimatedModule$15.execute (NativeAnimatedModule.java)
at com.facebook.react.animated.NativeAnimatedModule.executeAllOperations (NativeAnimatedModule.java)
at com.facebook.react.animated.NativeAnimatedModule.access$400 (NativeAnimatedModule.java)
at com.facebook.react.animated.NativeAnimatedModule$3.execute (NativeAnimatedModule.java)
at com.facebook.react.uimanager.UIViewOperationQueue$UIBlockOperation.execute (UIViewOperationQueue.java)
at com.facebook.react.uimanager.UIViewOperationQueue$1.run (UIViewOperationQueue.java)
at com.facebook.react.uimanager.UIViewOperationQueue.flushPendingBatches (UIViewOperationQueue.java)
at com.facebook.react.uimanager.UIViewOperationQueue.access$2600 (UIViewOperationQueue.java)
at com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.doFrameGuarded (UIViewOperationQueue.java)
at com.facebook.react.uimanager.GuardedFrameCallback.doFrame (GuardedFrameCallback.java)
at com.facebook.react.modules.core.ReactChoreographer$ReactChoreographerDispatcher.doFrame (ReactChoreographer.java)
at com.facebook.react.modules.core.ChoreographerCompat$FrameCallback$1.doFrame (ChoreographerCompat.java)
at android.view.Choreographer$CallbackRecord.run (Choreographer.java:1106)
at android.view.Choreographer.doCallbacks (Choreographer.java:866)
at android.view.Choreographer.doFrame (Choreographer.java:792)
at android.view.Choreographer$FrameDisplayEventReceiver.run (Choreographer.java:1092)
at android.os.Handler.handleCallback (Handler.java:938)
at android.os.Handler.dispatchMessage (Handler.java:99)
at android.os.Looper.loopOnce (Looper.java:226)
at android.os.Looper.loop (Looper.java:313)
at android.app.ActivityThread.main (ActivityThread.java:8680)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:567)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1135) |
|
People still tagging me like they haven't read the comments 😂. Please don't, thank you |
kelset
added
the
Needs: Repro
|
|
Unless someone can provide a repro with RN 0.69 of this issue we'll close this off. |
|
Hi @kelset , It's very hard to make a repro, because this issue happens only on some devices (samsung galaxy A13, Vivo V2118). Is it possible to add some checks on the node integrity before connecting it? |
closed means simply that there's nothing we can do about it. I hope you can understand that seeing constant notification on this issue by comments with really nothing to add is just adding noise on the maintainers. An alternative would be to lock it, and just tell people to submit PRs to try and improve the situation. Would that be better? |
As a disciplined, silent watcher of this issue, I support that 🙏 |
|
I just recorded this error today from google Robo testLab. I was using {
...[More steps]...
}, {
"sequence": 301,
"sourceScreenId": "73",
"destinationScreenId": "80",
"startTimeSeconds": 576.609728,
"endTimeSeconds": 578.248523,
"executionResult": "SUCCESS",
"target": {
"type": "SWIPE",
"childSequence": "0.0.1.0.1.0.0.0.0.0.0.0.1.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.0.1.0.0.0.1",
"targetDetails": {
"className": "y7.d",
"androidClassName": "android.widget.HorizontalScrollView"
}
}
}, {
"sequence": 302,
"sourceScreenId": "80",
"destinationScreenId": "80",
"startTimeSeconds": 578.897558,
"endTimeSeconds": 579.630209,
"executionResult": "SUCCESS",
"target": {
"type": "SWIPE",
"childSequence": "0.0.1.0.1.0.0.0.0.0.0.0.1.0.0.0.1.1.0.2",
"targetDetails": {
"className": "com.facebook.react.views.text.s",
"androidClassName": "android.widget.TextView",
"textLabel": "Início"
}
}
}, {
"sequence": 303,
"sourceScreenId": "80",
"destinationScreenId": "80",
"startTimeSeconds": 580.006176,
"endTimeSeconds": 581.236872,
"executionResult": "TERMINATED",
"target": {
"type": "TAP",
"childSequence": "0.0.1.0.1.0.0.0.0.0.0.0.1.0.0.0.1.1.0",
"targetDetails": {
"className": "com.facebook.react.views.view.g",
"androidClassName": "android.view.ViewGroup"
}
}
}]
}The step 301 was a single swipe on a HorizontalScroll list (with 12 items) until about 95% of it's end, |
|
the app is crashing on android 12 randomaly. com.facebook.react.bridge.JSApplicationIllegalArgumentException: connectAnimatedNodes: Animated node with tag (child) [290] does not exist |
As @kelset suggested, we're going to close and lock this issue for the time being. Sadly, the amount of users commenting with "same issue", "+1", or "any updates?" is increasing the maintainers burden for us all and is not bringing any value. The current status is the following:
We understand that this is creating issues for your apps & users, but in order to solve this we're going to accept only:
|
and others
Description
com.facebook.react.bridge.JSApplicationIllegalArgumentException: Animated node with tag 201 does not exists
at com.facebook.react.animated.NativeAnimatedNodesManager.connectAnimatedNodes(NativeAnimatedNodesManager.java:317)
at com.facebook.react.animated.NativeAnimatedModule$15.execute(NativeAnimatedModule.java:681)
at com.facebook.react.animated.NativeAnimatedModule.executeAllOperations(NativeAnimatedModule.java:258)
at com.facebook.react.animated.NativeAnimatedModule.access$400(NativeAnimatedModule.java:85)
at com.facebook.react.animated.NativeAnimatedModule$3.execute(NativeAnimatedModule.java:287)
at com.facebook.react.uimanager.UIViewOperationQueue$UIBlockOperation.execute(UIViewOperationQueue.java:573)
at com.facebook.react.uimanager.UIViewOperationQueue$1.run(UIViewOperationQueue.java:908)
at com.facebook.react.uimanager.UIViewOperationQueue.flushPendingBatches(UIViewOperationQueue.java:1019)
at com.facebook.react.uimanager.UIViewOperationQueue.access$2600(UIViewOperationQueue.java:47)
at com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.doFrameGuarded(UIViewOperationQueue.java:1079)
at com.facebook.react.uimanager.GuardedFrameCallback.doFrame(GuardedFrameCallback.java:29)
at com.facebook.react.modules.core.ReactChoreographer$ReactChoreographerDispatcher.doFrame(ReactChoreographer.java:175)
at com.facebook.react.modules.core.ChoreographerCompat$FrameCallback$1.doFrame(ChoreographerCompat.java:85)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1140)
at android.view.Choreographer.doCallbacks(Choreographer.java:946)
at android.view.Choreographer.doFrame(Choreographer.java:870)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1127)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:210)
at android.os.Looper.loop(Looper.java:299)
at android.app.ActivityThread.main(ActivityThread.java:8085)
at java.lang.reflect.Method.invoke(Method.java:-2)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:556)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1045)
Version
0.64.2
Output of
npx react-native infoSystem:
OS: macOS 11.4
CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
Memory: 65.65 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.10.0 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 7.24.0 - /usr/local/bin/npm
Watchman: 2021.09.13.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
Android SDK:
API Levels: 23, 25, 27, 28, 29, 30
Build Tools: 28.0.3, 29.0.2, 30.0.2
System Images: android-29 | Intel x86 Atom_64
Android NDK: 22.1.7171670
IDEs:
Android Studio: 4.2 AI-202.7660.26.42.7351085
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_292 - /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.2 => 0.64.2
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
App crashes randomly in Android
Snack, code example, screenshot, or link to a repository
No response
The text was updated successfully, but these errors were encountered: