You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reanimated 2 is primarily built in C++ using Turbo Modules infrastructure which is not yet completely deployed in React Native (specifically on Android). Because of that the installation of new Reanimated requires additional steps apart from just adding a dependency to package.json.
This means that the following method needs to be overridden in the ElectrodeReactNativeHost, something that the current ReactPlugin interface doesn't provide.
Besides the new JSIModulePackage there is another difference in how the android module is generated for this dependency: during the package creation the android-npm folder is added as the android one (createNPMPackage.sh#L82). As you can see the ReanimatedProxyPackage.java is empty in this case, and this is because the aar packages are generated directly and picked up during the build time.
We haven't found a way to support all these changes needed for react-native-reanimated v2.0.0 in our manifest yet.
Any help is appreciated.
The text was updated successfully, but these errors were encountered:
This version is different from the current supported version (react-native-reanimated_v1.3.0+). According to the documentation:
This means that the following method needs to be overridden in the
ElectrodeReactNativeHost
, something that the current ReactPlugin interface doesn't provide.Besides the new JSIModulePackage there is another difference in how the android module is generated for this dependency: during the package creation the android-npm folder is added as the android one (createNPMPackage.sh#L82). As you can see the ReanimatedProxyPackage.java is empty in this case, and this is because the aar packages are generated directly and picked up during the build time.
We haven't found a way to support all these changes needed for react-native-reanimated v2.0.0 in our manifest yet.
Any help is appreciated.
The text was updated successfully, but these errors were encountered: