-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
🐛 Reanimated 3.5.4 + RNVC V3 Frame Processor causes app crashes(signal SIGABRT) #1843
Comments
Hey! Hmm, maybe there is some incompatibility with the Babel plugins? Which one do you use? Both REA and Worklets? The log output is not really relevant in this case, did you run the app through Xcode? Is there a stacktrace shown on the left? |
@mrousavy I didn't touch the existing babel.config.js at all. Here are the logs from
|
Hm, idk there are no native changes since REA 3.5.0, and I remember that 3.5.0 worked at some point. Maybe there is something wrong happening in the worklets, I can try to debug this once I'm done with the new devices API/docs! |
Could it be that the new version has some updates in the babel plugin architecture (which will be automatically updated by upgrading Reanimated) - or that having two babel plugins for worklets makes for some undefined behaviour? Could you remove the worklet plugin after installing Reanimated and report back with your findings? (in the babel.config.js file). |
@chrfalch I've already tried switching the order of plugins, but the crash still occurred.
Does this mean leaving |
Yes, that was the suggestion. The theory was that the two might be interfering with each other. |
I tested removing |
Okay then it might be a REA compatibility thing? We need to check what has changed since their last release. Alternatively, you could downgrade REA but that's also not an ideal solution. It sucks that we have to have two separate Worklet implementations :/ |
+1 Just ran into this as well.
I tested with REA v EDIT: Did a bit more testing and looks like this issue begins to appear with REA v |
REA v 3.5.0 mean "react-native-reanimated": "^3.5.0" ? @jackster-humi |
"react-native-reanimated": "^3.4.2", |
Yes, that's correct, I was referring to I've written a face detector I'll try to spend some time this weekend getting a good stracktrace + minimum reproducible example. I'm now also getting a similar crash when upgrading reanimated from
|
I encountered an interesting yet positive occurrence. I updated my RNVC version from 3.2.2 to 3.4.0 while keeping Reanimated at 3.3.0. This led to a crash in my app. However, when I examined the crash log, it seemed strangely familiar, and I recalled encountering the same error message before. In an attempt to resolve the issue, I decided to upgrade Reanimated to 3.5.4, hoping for a stroke of luck. Surprisingly, it resolved the problem. To sum it up: RNVC 3.2.2 + Reanimated 3.3.0 → Functioning properly |
Gotcha, I think I know a fix @bglgwyng |
@pvducTaureauAI Have you tried the example app in the package? Which platform do you have problems with? |
does it work? |
@chrfalch just fixed this issue in this PR (I think) - we'll test more then release an update! margelo/react-native-worklets-core#128 |
What's happening?
I bumped Reanimated version up to 3.5.4 and my app crashed immediately after launched.
When I unset
frameProcessor
props, the crash was gone.Reproduceable Code
https://github.com/bglgwyng/react-native-vision-camera/tree/reanimated-3.5.4
The only thing I did was install reanimated 3.5.4.
You could observe that commenting
frameProcessor
props prevents the crash from occurring.Relevant log output
Camera Device
Device
iPhone 13 (iOS 16.6.1)
VisionCamera Version
3.0.0
Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information
The text was updated successfully, but these errors were encountered: