App immediately crash using runOnJS?

[gpbaculio]

app closing immediately

Expected behavior

Actual behavior & steps to reproduce

Snack or minimal code example

  const setIngredient = useCallback(() => {
    setState({
      ...state,
      [ingredient]: Math.max(...Object.values(state)) + 1,
    });
  }, [state, ingredient, setState]);
  const onGestureEvent = useAnimatedGestureHandler({
    onActive: ({ translationX, translationY }) => {
      translateX.value = translationX;
      translateY.value = translationY;
    },
    onEnd: ({ velocityY }) => {
      "worklet";

      const destination = snapPoint(translateY.value, velocityY, [
        0,
        -HEADER_HEIGHT,
      ]);
      translateX.value = withTiming(0);
      translateY.value = withTiming(0, {}, () => {
        opacity.value = 1;
      });
      if (destination !== 0) {
        opacity.value = 0;
        runOnJS(setIngredient)();
      }
    },
  });

Package versions

• React Native: 0.64
• React Native Reanimated: 2.1.0
• NodeJS: v12.21.0
• Xcode: 12.5
• Java & Gradle:

Affected platforms

• [ x] Android
• [ x] iOS
• Web

[github-actions]

Issue validator

The issue is invalid!

• Section required but not found: description(for label 🐞 bug)
• Section expected behavior seems to be empty(for label 🐞 bug)
• Section actual behavior & steps to reproduce seems to be empty(for label 🐞 bug)

[mrousavy]

Could you share your native logs?

In Xcode open the "Debug Area", in Android Studio show "Logcat" (or run adb logcat), then share the relevant lines here.

[gpbaculio]

@mrousavy this is on my system log when it closes:

(UIKitApplication:org.reactjs.native.example.rnPizzaAnimated[dd03][rb-legacy][31448]): Service exited due to SIGBUS | sent by exc handler[31448]

and my stackoverflow question.

[jmysliv]

Hi @gpbaculio! Are you still encounter this issue? Have you tried to upgrade reanimated to 2.3.0-alpha.2?

[gpbaculio]

@jmysliv updating react + reanimated fix

[GunnarAK]

For any people that are currently running into this with Reanimated v3.5:

I had this very similar issue as well with the following snippet in my Splashscreen component

opacity.value = withTiming(0, { duration: fadeOutTime }, () =>
  runOnJS(setBootSplashIsVisible)(false),
);

The issue was related to Reanimated 3.5.1 and the issue was fixed in 3.5.2. I upgraded to this and could confirm it was fixed. Upgrading to current latest (3.5.4) also proved it was fixed. 🚀