-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
No aar for react-native-reanimated found. #2650
Comments
Issue validatorThe issue is valid! |
Also tried with "react-native-reanimated": "react-native-reanimated@2.3.0-alpha.2", |
Hi! Edit: you may also try downgrading version of We are currently working on building from source on client side but it is not there yet. |
This issue goes away when react-native version is upgraded to 0.63.x as mentioned by @kkafar. Thanks! |
Seems to be still present with Expo framework 44.0.0, based on react-native 0.64.3 (react-native-reanimated 2.3.1): while trying to build my app for F-Droid, I saw the same error. See https://gitlab.com/marcoXbresciani/fdroiddata/-/jobs/1944767156 line 2438. |
Hi I'm still getting this issue for v2.8.0. Any idea how to fix this? |
Still issue in RN |
Same issue using: This version fix the issue: |
now failing expo/eas builds |
Issue with react-native 0.70.1 |
Experiencing this issue on react-native 0.63.3 |
Experiencing this with
Versions:
|
I'm experiencing the same thing when building with EAS |
Experiencing this issue on react-native 0.65.3 |
Same issue with react-native 0.70.5 |
Running I'm with RN@0.70.5 and react-native-reanimated@2.12.0. I guess it's probably cleaning the cmake cache. |
I'm no longer on reanimated team, but if I recall correctly each version of Please, note also that versions To resolve the issue you should try
|
Comment this comment and after the case, how the file exists: |
I have tried with react-native 0.71.3 and latest react-native-reanimated 3.0.1, yet still receive this warning, and now it just stuck on configuring at 63%
|
For me, this fixed it: "react-native": "0.71.3", |
Downgrade to 2.2.2 solved for me |
In Reanimated 3, we no longer provide binaries in the npm package. You need to install NDK then Reanimated will build from the source. |
same issue, im using |
i have same error, using "react-native": "0.71.7", |
the following did help me: Open Android Studio That’s it! It took a couple minutes for Android Studio to finish opening the project for the first time, but the src&credits: |
I am also getting this issue and struggling to find a fix. Any clues? |
i have same issue on android only, using "react-native": "0.71.7", |
it worked for me when I downgraded "react-native-reanimated" to "2.2.4" |
Why ? or how did you provide them in new way ? |
|
Co-ask please? |
Hey guys, Pinging here about Reanimated 3 and the AAR. My understanding is that as long as NDK is installed with Android Studio, Reanimated 3 should work for Android with However, I have NDK version 23.1.7779620 installed (verified from Project Structure/Modules) and am still getting the error:
Is there a step I'm missing for building Reanimated 3? I have no problem if I downgrade to 2, but would prefer 3. Thanks! |
When it comes to:
To avoid weird crashes while using the app, we need to have different versions of the binaries for different configurations. This includes the last 3 versions of React Native, all the patch versions for each of those versions (which averages to about 5 patches per version), 2 different runtime types (Herems and JSC), and the last 3 NDK versions. We end up with 90 different versions of the app (3 x 5 x 2 x 3 = 90). Each of these versions is about 4MB in size, which adds up to 360MB in total - which is over the NPM package size limit. To solve this problem, we've decided not to include all 90 versions in the package anymore. Instead, we'll build the necessary Reanimated binaries from the source while the user builds the app on their machine. |
Configure project :react-native-reanimated FAILURE: Build failed with an exception.
|
Please help, I am not able to build :react-native-reanimated after upgrading to ubuntu 23. |
Still not working. When i need to add |
After update to RN 72.3 and update "react-native-reanimated": "^3.0.2" |
Having this issue in react-native |
any solution ? facing on |
"react-native": "0.72.4" So is there any way at all to use Reanimated? P.S. To follow up, for me this turned out to be a weird Ubuntu problem with cmake: I had a Python script wrapping |
I have recently cloned my repository from GitHub, and I had also encountered the same issue. The functionality was working perfectly before I cloned the project. Here are the relevant dependencies from my project's configuration:
To resolve this issue, I followed these steps:
By following these steps, I was able to successfully overcome the problem and restore the functionality of my project. |
i have this warning below when runing on android WARNING reanimated - no version-specific reanimated AAR for react-native version 72 found. |
I am a React developer and was about to work on a React Native project. I faced many issues during my project setup. Most of them were wrong PATH settings and less permissions issues. So, I found a solution to create a Also I faced an issue while installing NDK from Android Studio SDK Manager and that was of no permissions being granted to Android Studio although other Tools were successfully installed without any such issue. |
Thanks for your response but my android is working perfectly but iOS is
crashing when navigation happens
…On Tue, Sep 5, 2023, 9:36 PM Abdullah Sajjad ***@***.***> wrote:
I am a React developer and was about to work on a React Native project. I
faced many issues during my project setup. Most of them were wrong PATH
settings and less permissions issues.
In my case, the reason of this error was that my *ndk path* was not being
put correctly when building so the gradle considered that NDK was not
installed. I also reinstalled NDK but then I found that the issue is path
being wrong.
So, I found a solution to create a local.properties file in android
folder root and put ndk.dir = NDK_PATH_HERE where my ndk path was like
/Users/USERNAME/Library/Android/sdk/ndk/25.2.9519653.
Also I faced an issue while installing *NDK* from *Android Studio SDK
Manager* and that was of no permissions being granted to Android Studio
although other Tools were successfully installed without any such issue.
This question Stack Overflow
<https://stackoverflow.com/questions/43042032/android-studio-fails-to-install-update-error-failed-to-read-or-create-install>
and specifically this command sudo chown -R $USER: $ANDROID_HOME helped
me solve it.
—
Reply to this email directly, view it on GitHub
<#2650 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVORBTKP7ZKE6RKABYED6B3XY6ELJANCNFSM5IQGHO6A>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
For me this was caused by an empty sdkmanager --install "ndk;23.1.7779620" I also needed to install cmake: sdkmanager --install "cmake;3.22.1" |
I confirm that this solution works. |
thanks mate, this solution works. |
Anu suggestion for "react": "18.2.0", |
Description
No aar for react-native-reanimated found.
Expected behavior
Android build should work
Actual behavior & steps to reproduce
Gradle log
Package versions
Affected platforms
The text was updated successfully, but these errors were encountered: