-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
android : Failed to resolve #21907
Comments
I have the same problem at this morning. |
Same here, yesterday it was working fine |
Moving the jcenter repository to the last position fixed the issue for me: before:
And after the fix:
|
Looks like someone (again?) mistakenly uploaded an incomplete Android support package to |
Fixes facebook#21907 (comment) and prevent similar issues happening again
CI is broken on Android since today, applying a quick workaround to keep CI green while the react-native team figures it out. See: - facebook/react-native#21910 - facebook/react-native#21907
@kmend Don't close the issue. And make the title more obvious so that some core members could see this soon. |
Switching the order of |
Summary: Fixes #21907 (comment) and prevent similar issues happening again Pull Request resolved: #21910 Differential Revision: D10842256 Pulled By: hramos fbshipit-source-id: f4abaa1c8ff8df6f0fb57b1bad745f4df9da7143
Switching the order of jcenter() and google() didn't work for me... [2] |
Make sure you have found the right file and the right place to switch google() and jcenter() |
"react": "16.6.0-alpha.8af6728", Android Studio 3.2.1 // Top-level build file where you can add configuration options common to all sub-projects/modules. buildscript {
} allprojects { task wrapper(type: Wrapper) { Broken |
Thank you @nvelozsavino , moving jcenter() to last position fixed the issue. |
Switching the order of |
Not sure it's 100% the same issue but I emailed jfrog support about a similar thing a while ago, they did reply but we continued to experience occasional issues for some time after, has seemed ok lately though. Switching
|
I get the same issue and switching jcenter to the last position isn't working for me.
|
Did somebody find the solution? Switching jcenter to last position doesn't work for me. |
I have it like this on the gradles and is building just fine |
@filipef101 No luck, it doesn't work for me. Are there any other ways to solve this problem? |
@YuriyNskiy - It may be one of your react-native libraries in your package.json that are failing when building the react-native application. I kept getting this error:
React-native-camera updated their build.gradle file and all I pulled the latest changes and voila... My react-native-camera module. Check to see if any of your external libraries have been updated. If you do get an error with your libraries you could update the library's build.gradle file in node_modules/{libraryFolder}/android/buidle.gradle (not a solution btw, just a process of elimination to see if the error is coming form the libraries) |
@YuriyNskiy I'm not sure if it is the correct aproach but I have that on build.gradle on the /android root and on the android/app dir
|
@filipef101 approach that works for me: My root build.gradle file:
|
Summary: Fixes facebook/react-native#21907 (comment) and prevent similar issues happening again Pull Request resolved: facebook/react-native#21910 Differential Revision: D10842256 Pulled By: hramos fbshipit-source-id: f4abaa1c8ff8df6f0fb57b1bad745f4df9da7143
Summary: Fixes facebook#21907 (comment) and prevent similar issues happening again Pull Request resolved: facebook#21910 Differential Revision: D10842256 Pulled By: hramos fbshipit-source-id: f4abaa1c8ff8df6f0fb57b1bad745f4df9da7143
Environment
Run
react-native info
in your terminal and paste its contents here.React Native Environment Info:
System:
OS: macOS 10.14
CPU: x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Memory: 740.27 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 8.11.2 - /usr/local/bin/node
Yarn: 1.10.1 - /usr/local/bin/yarn
npm: 5.6.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
Android SDK:
Build Tools: 23.0.1, 23.0.2, 23.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.3, 28.0.3
API Levels: 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28
IDEs:
Android Studio: 3.2 AI-181.5540.7.32.5056338
Xcode: 10.0/10A255 - /usr/bin/xcodebuild
npmPackages:
react: 16.6.0-alpha.8af6728 => 16.6.0-alpha.8af6728
react-native: 0.57.3 => 0.57.3
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7
Description
Describe your issue in detail. Include screenshots if needed. If this is a regression, let us know.
android
react-native init AwesomeProject
open android studio
err:
The option 'android.enableAapt2' is deprecated and should not be used anymore.
Use 'android.enableAapt2=true' to remove this warning.
It will be removed at the end of 2018..
Failed to resolve: support-vector-drawable
Open File
Failed to resolve: livedata-core
Open File
Failed to resolve: viewmodel
Open File
Failed to resolve: common
Open File
Failed to resolve: runtime
Open File
Reproducible Demo
Let us know how to reproduce the issue. Include a code sample, share a project, or share an app that reproduces the issue using https://snack.expo.io/. Please follow the guidelines for providing a MCVE: https://stackoverflow.com/help/mcve
The text was updated successfully, but these errors were encountered: