Rohith S Moolya
06/19/2025, 9:26 AM./gradlew assembleDebug, but I keep running into a Gradle failure related to dependency resolution.
The error occurs during the :app:checkDebugAarMetadata task and says that it can’t find any version of com.facebook.react:react-native. Here’s the relevant part of the logs:
> Task :app:checkDebugAarMetadata FAILED
* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
> Could not find any matches for com.facebook.react:react-native:+ as no versions of com.facebook.react:react-native are available.
Searched in the following locations:
-
<https://dl.google.com/dl/android/maven2/com/facebook/react/react-native/maven-metadata.xml>
- <https://repo.maven.apache.org/maven2/com/facebook/react/react-native/maven-metadata.xml>
- <https://repo.maven.apache.org/maven2/com/facebook/react/react-native/0.71.0-rc.0/react-native-0.71.0-rc.0.pom>
- <https://www.jitpack.io/com/facebook/react/react-native/maven-metadata.xml>
- <https://maven.google.com/com/facebook/react/react-native/maven-metadata.xml>
- file:/path/to/node_modules/react-native/android/com/facebook/react/react-native/maven-metadata.xml
- file:/path/to/node_modules/jsc-android/dist/com/facebook/react/react-native/maven-metadata.xml
Has anyone faced this before? I'm wondering if this might be related to using + in the dependency version or a missing local Maven repo. Appreciate any suggestions! 🙏Thomas Broyer
06/19/2025, 9:37 AM+, along with a borked repository (you may want to report that to Sonatype). But given that this project has been relocated to new coordinates, you'd better update your project to that rather than, say, using the previous react-native version from 9 years ago!Vampire
06/19/2025, 1:35 PM+, but have the according react native Gradle plugin version?Vampire
06/19/2025, 1:35 PM