Easing in Keyframe causes fatal crash on Android

[AdamGerthel]

Description

When using custom easings (i.e. non-default) on keyframe animations, the application crashes with the following error:

JS Functions are not convertible to dynamic

Error: JS Functions are not convertible to dynamic
at workletValueSetter (/node_modules/react-native-reanimated/src/reanimated2/core.ts
at workletValueSetter
at startAnimationForTag

Steps to reproduce

Create an Animated.View with an entering Keyframe sequence that uses Easing.ease and have it render. The same problem occurs with other easings such as Easing.out(Easing.exp) but not with Easing.out(Easing.quad) or Easing.in(Easing.quad).

Snack or a link to a repository

https://snack.expo.dev/@insats/bug---reanimated-easing-in-keyframe-android

Reanimated version

2.14.4 in my project and 2.9.1 in the snack sample. Same problem in both.

React Native version

0.68.1 in my project and Expo v46 (0.69.5) in the snack sample.

Platforms

Android

JavaScript runtime

None

Workflow

None

Architecture

Paper (Old Architecture)

Build type

None

Device

Real device

Device model

No response

Acknowledgements

Yes

[graszka22]

Your Snack link doesn't work (oh no something ate it 🤣).

I tried to reproduce it like this: https://snack.expo.dev/wty2brqIH?platform=android with Easing.out(Easing.exp) but it works on my Android. Could you upload your snack again (and check if it works)?

[AdamGerthel]

@graszka22 there was a type in the URL. Try it now!

Update
Yours doesn't work either, when using Easing.ease: https://snack.expo.dev/@insats/fascinated-mixed-nuts?platform=android

[graszka22]

Ok, I can reproduce it 👍 But I've tried also running on the main branch of reanimated and it seems to work, no crashes, the dot is moving. Can you try it too?

[AdamGerthel]

@graszka22 I haven't been able to build my project for Android using reanimated v3, but I tried it with a fresh RN project and it works there. That definitely narrows it down, right?

EDIT: Also, is v3 compatible with RN 0.68.1? I'm trying to decide if I should refactor my animations to use useAnimatedStyle instead of layout animations or attempt an upgrade, while waiting for this issue to be resolved. Upgrading RN is not an option for me right now.

[graszka22]

If it works with v3 then I assume the issue is fixed?

[AdamGerthel]

@graszka22 Well, it still needs to be fixed for v2 if v2 is still maintained, right?

[graszka22]

We're ending maintenance for v2. We're planning only support for RN 72 and simple fixes. This is probably not a simple fix.
I'm suspecting this issue is solved by recent shareable values rewrite.
v3 is compatible with RN 0.68.1 on Paper architecture. You shouldn't have to change anything in your project to upgrade reanimated v2 to v3, unless you use reanimated v1 api.

[AdamGerthel]

I manage to build it on Android now with v3, after fixing this and removing this. Seems to be working well.

[graszka22]

Great 👏 if all seems to be working, I'm closing the issue.