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
Recent versions of react-native have caused this error:
Im using the following packages for my expo app
I've found a partial fix:
Within CMakeLists.txt remove ReactAndroid::turbomodulejsijni & ReactAndroid::react_nativemodule_core
Replace with ReactAndroid::reactnative
For anyone unsure on how to apply this fix, search into npm patch-package or pnpm patch.
Im unable to test this fix fully due to the prisma/react-native C++ bindings failed to initialize error. However, the above fix atleast allows the app to build
The text was updated successfully, but these errors were encountered:
Jamie-Fairweather
changed the title
[Temp Fix] Execution failed for task 'prisma_react-native:configureCMakeDebug[arm64-v8a]'.
Execution failed for task 'prisma_react-native:configureCMakeDebug[arm64-v8a]'.
Dec 1, 2024
After some more digging into the prisma/react-native C++ bindings failed to initialize error, it seems either react-native-quick-base64 or @prisma/react-native just doesn't support the new expo architecture (enabled by default for sdk 52 and react-native 0.76)
Recent versions of react-native have caused this error:
Im using the following packages for my expo app
I've found a partial fix:
Within CMakeLists.txt remove
ReactAndroid::turbomodulejsijni
&ReactAndroid::react_nativemodule_core
Replace with
ReactAndroid::reactnative
For anyone unsure on how to apply this fix, search into
npm patch-package
orpnpm patch
.Im unable to test this fix fully due to the
prisma/react-native C++ bindings failed to initialize
error. However, the above fix atleast allows the app to buildThe text was updated successfully, but these errors were encountered: