Conversation
…-mansion/react-native-reanimated into @piaskowyk/rn73-nightly-android
|
@efstathiosntonas Thanks for the reminder! Looks like this PR already contains these changes:
|
|
@piaskowyk Hi, can you check this comment? #4913 (comment) |
|
Hey, could you tell me how I can reproduce this error? |
|
@piaskowyk |
) # Why In order to have the react-native 73 upgrade PR ready by the end of the week we will need to temporarily bump react-native-reanimated to a nightly version, given that software-mansion/react-native-reanimated#4913 has not been officially released yet. # How `et uvm -m react-native-reanimated -c f06ee065904ebeac3fa72d4bda32ba3360bf49e7 -s 3.6.0-nightly-20231031-c56d44fd9` # Test Plan Run locally expo go unversined and bare-expo # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
|
Would be nice to see this released, react-native 0.73 is on rc4 now and should go out soon Cheers |
|
Hello, thanks for you work. Pending the time this is released, what are the steps if i want to use react-native-reanimated from the main branch. i tried to add it by doing this in package.json which works when building locally, but when doing a release build it breaks with this error |
|
@daviddamilola I'm in a similar situation. 😅 you may give nightly builds a try:
worked for me with |
|
Thanks @altaywtf , will try it out. |
+1 Using the nightly does not seem to solve the problem. Not sure whether anything is wrong on my side. |
Hello, i can confirm the error remains for v0.73.0-rc.4 but works for v0.73.0-rc.1 |
It seems that this issue is fixed by bf7df79. I've tried on the latest nightly and the build error no longer shows up. |
…o#25161) # Why In order to have the react-native 73 upgrade PR ready by the end of the week we will need to temporarily bump react-native-reanimated to a nightly version, given that software-mansion/react-native-reanimated#4913 has not been officially released yet. # How `et uvm -m react-native-reanimated -c f06ee065904ebeac3fa72d4bda32ba3360bf49e7 -s 3.6.0-nightly-20231031-c56d44fd9` # Test Plan Run locally expo go unversined and bare-expo # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
Did you find the solution for this? |
|
@mohan-sprinklr IMHO, this should have been fixed in the latest release of react-native-reanimated. Would you mind confirm whether clearing build cache, re-running pod install and re-building the APP helps? |
I am still getting the issue in react-native-reanimated latest version i.e 3.8.0 I cleared pod cache --> deleted Pods folder --> reinstalled pods --> cleared build folder inside xcode --> manually deleted xcode cache inside /Users//Library/Developer/Xcode |
|
I think commenting the enableDebugging and disableDebugging option in "node_modules>react-native-reanimated>Common>cpp>ReanimatedRuntime>ReanimatedHermesRuntime.cpp" is better. SInce React Native has deprecated Remote JavaScript Debugging. I can no longer see the option in Android dev-menu to remote debug. And the above methods are shown in dev-menu for ios earlier but now are deprecated but still being used by reanimated(I assume). So commenting them makes the build run successfully. also @mohan-sprinklr , disabling hermes in debug did not fix the issue for me. If anyone wants to use remote debugging they can follow this official guide - https://reactnative.dev/docs/next/other-debugging-methods. Which works on both ios and android. |


Summary
The PR adds support for react-native@0.73.
Related changes in react-native
Paper
According to documentation, we can do it safely - https://developer.android.com/reference/tools/gradle-api/7.0/com/android/build/api/dsl/BuildFeatures#buildConfig:kotlin.Boolean
Fabric
Backward compatibility