-
Notifications
You must be signed in to change notification settings - Fork 8
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
React-native Android build error: no compatible library found for //ReactAndroid/fabricjni #13
Comments
The error is Can you give this a try? google/oboe@583c0af |
I have this one defined here |
From the ChatGPT The error you’re seeing is related to a mismatch between the expected type of Standard Template Library (STL) the project is using (static vs shared) when building native code. Specifically, the message indicates that the user is using a static STL, but the library ReactAndroid/fabricjni requires a shared STL. Here are some steps you can take to try to resolve this issue:
By following these steps, you should be able to mitigate or resolve the STL conflict and proceed with the build. If the issue still exists, refer to the relevant documentation or reach out to the community for more specific guidance. |
Closed without response |
Hello. Thanks for the project, I'm trying to get the example running locally on Android. The error I've been stuck with is the following:
Entire log:
Can you please help me with getting the react native (expo) example running on Android device ? Thanks a lot in advance.
Note: had to make a few edits to library code before I got to this error - i.e. there is a release url referenced in gradle which was no longer valid and was replaced with
https://github.com/nihui/opencv-mobile/releases/download/v27/opencv-mobile-4.9.0-android.zip
. These seem harmless enough but if you'd like to see them as well happy to provide.Note2: as farbic is mentioned in error, I tried to run the same code but toggling the "newArchitecture" option in gradle.options to true - this fails elsewhere.
The text was updated successfully, but these errors were encountered: