-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task :app:configureCMakeRelWithDebInfo[arm64-v8a] FAILED #47917
Comments
Warning Could not parse version: We could not find or parse the version number of React Native in your issue report. Please use the template, and report your version including major, minor, and patch numbers - e.g. 0.76.2. |
Warning Could not parse version: We could not find or parse the version number of React Native in your issue report. Please use the template, and report your version including major, minor, and patch numbers - e.g. 0.76.2. |
Hey @patel-harshal, Remove all white spaces from your app path and try again. |
This issue is waiting for author's feedback since 24 days. Please provide the requested feedback or this will be closed in 7 days. |
This issue was closed because the author hasn't provided the requested feedback after 7 days. |
Description
Task :app:configureCMakeRelWithDebInfo[arm64-v8a]
C/C++: CMake Error at A:/React Native/signalgroupapp/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:42 (add_library):
WARNING reanimated - no version-specific reanimated AAR for react-native version 76 found.
Falling back to AAR for react-native version 71.
The react-native JSI interface is not ABI-safe yet, this may result in crashes.
Please post a pull request to implement support for react-native version 76 to the reanimated repo.
Thanks!
Steps to reproduce
./gradlew assembleRelease
React Native Version
0.75
Affected Platforms
Runtime - Android
Areas
Other (please specify)
Output of
npx react-native info
Stacktrace or Logs
Reproducer
https://github.com/patel-harshal/MY_DB
Screenshots and Videos
No response
The text was updated successfully, but these errors were encountered: