react-native-reanimated: Reanimatedv2 Task :app:checkDebugAarMetadata FAILED

Description


> Task :app:checkDebugAarMetadata FAILED

* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Failed to transform react-native-reanimated-64.aar (project :react-native-reanimated) to match attributes {artifactType=android-aar-metadata}.
      > Execution failed for JetifyTransform: /aaa-reactnative/node_modules/react-native-reanimated/android/react-native-reanimated-64.aar.
         > Transform's input file does not exist: /aaa-reactnative/node_modules/react-native-reanimated/android/react-native-reanimated-64.aar. (See https://issuetracker.google.com/issues/158753935)

Steps To Reproduce

  1. yarn react-native run-android

Package versions

  • React: 17.0.1
  • React Native: 0.64.0-rc.2
  • React Native Reanimated: ^2.0.0-rc.2
  • NodeJS: v14.15.3

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 1
  • Comments: 29 (6 by maintainers)

Commits related to this issue

Most upvoted comments

Please let me know anyone got a fix.

I’m facing the below issues

What went wrong: A problem occurred evaluating project ‘:react-native-reanimated’.

Task with path ‘:app:mergeDebugNativeLibs’ not found in project ‘:app’.

reactnative/node_modules/react-native-reanimated/android/react-native-reanimated-6*.aar. Just go to the above path and copy the files and rename what is required, For example, if the problem is not finding 66.aar copy & paste the previous main aar file and hermen aar file in the path and rename it with 66

Hey @productfrontenddeveloper We haven’t support react-native@0.64 yet. I made PR who has added this support for android. I think we will add this within the next release.

in my case I have installed react-native-reanimated@2.3.0-alpha.2 and it works… I have tried with alpha3 but it returns an error in my project

createNPMPackage is a script that will work only in Reanimated repository, you can’t copy it to your project and build Reanimated from there.

Follow instructions written by @piaskowyk, that is:

  • clone Reanimated repo
  • install packages by running yarn
  • and then run the createNPMPackage script in order to generate the npm package.

Then you can go to your project and install generated .tgz:

yarn add file:/path/to/local/tarball.tgz installs a package from a gzipped tarball which could be used to share a package before publishing it.

https://classic.yarnpkg.com/en/docs/cli/add/#toc-adding-dependencies

Yes, I got it twice in my notifications. Please don’t tag maintainers that often, we dedicate only part of our time to checking issues and we definitely can see responses and tagging. Issues are dedicated to actual bugs. We don’t usually provide support for problems with builds or configs, those should be submitted in QA section of Discussions.

That being said, I suppose you still try building reanimated in the node_modules, this won’t work. The only way to generate a package is to follow the advice written by @piaskowyk here or reiterated by me here.

The simplest way though is to wait for the release which should happen in the next few days. You can also use daily builds, instructions are described in the documentation.