Fixed
Status Update
Comments
an...@gmail.com <an...@gmail.com> #2
me...@gmail.com <me...@gmail.com> #3
jc...@gmail.com <jc...@gmail.com> #4
looks like google() is not working as expected and you have to manually add a maven entry for every library you need
st...@gmail.com <st...@gmail.com> #5
uc...@google.com <uc...@google.com>
[Deleted User] <[Deleted User]> #7
It also missing firebase-plugins dependency
Could not find com.google.firebase:firebase-plugins:1.1.5.
Searched in the following locations:
-https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-plugins/1.1.5/firebase-plugins-1.1.5.pom
-https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-plugins/1.1.5/firebase-plugins-1.1.5.jar
-https://jcenter.bintray.com/com/google/firebase/firebase-plugins/1.1.5/firebase-plugins-1.1.5.pom
-https://jcenter.bintray.com/com/google/firebase/firebase-plugins/1.1.5/firebase-plugins-1.1.5.jar
Could not find com.google.firebase:firebase-plugins:1.1.5.
Searched in the following locations:
-
-
-
-
pa...@gmail.com <pa...@gmail.com> #8
The problem persists... I'm having the following error...
* Where:
Build file '/home/patricio/infomigra_app/platforms/android/build.gradle' line: 95
* What went wrong:
A problem occurred evaluating root project 'android'.
> Could not resolve all dependencies for configuration 'classpath'.
> Could not find any matches for com.android.tools.build:gradle:+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml
https://jcenter.bintray.com/com/android/tools/build/gradle/
file:/home/patricio/.m2/repository/com/android/tools/build/gradle/maven-metadata.xml
file:/home/patricio/.m2/repository/com/android/tools/build/gradle/
Required by:
unspecified:unspecified:unspecified
* Where:
Build file '/home/patricio/infomigra_app/platforms/android/build.gradle' line: 95
* What went wrong:
A problem occurred evaluating root project 'android'.
> Could not resolve all dependencies for configuration 'classpath'.
> Could not find any matches for com.android.tools.build:gradle:+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
file:/home/patricio/.m2/repository/com/android/tools/build/gradle/maven-metadata.xml
file:/home/patricio/.m2/repository/com/android/tools/build/gradle/
Required by:
unspecified:unspecified:unspecified
br...@gmail.com <br...@gmail.com> #9
Ouch we got bit by this too. Do we have a resolution estimate?
14:05:31 > Could not resolve all artifacts for configuration ':classpath'.
14:05:31 > Could not find com.google.gms:google-services:4.0.1.
14:05:31 Searched in the following locations:
14:05:31 - file:/var/lib/jenkins/.m2/repository/com/google/gms/google-services/4.0.1/google-services-4.0.1.pom
14:05:31 - file:/var/lib/jenkins/.m2/repository/com/google/gms/google-services/4.0.1/google-services-4.0.1.jar
14:05:31 -https://dl.google.com/dl/android/maven2/com/google/gms/google-services/4.0.1/google-services-4.0.1.pom
14:05:31 -https://dl.google.com/dl/android/maven2/com/google/gms/google-services/4.0.1/google-services-4.0.1.jar
14:05:31 -https://jcenter.bintray.com/com/google/gms/google-services/4.0.1/google-services-4.0.1.pom
14:05:31 -https://jcenter.bintray.com/com/google/gms/google-services/4.0.1/google-services-4.0.1.jar
14:05:31 -https://maven.fabric.io/public/com/google/gms/google-services/4.0.1/google-services-4.0.1.pom
14:05:31 -https://maven.fabric.io/public/com/google/gms/google-services/4.0.1/google-services-4.0.1.jar
14:05:31 > Could not resolve all artifacts for configuration ':classpath'.
14:05:31 > Could not find com.google.gms:google-services:4.0.1.
14:05:31 Searched in the following locations:
14:05:31 - file:/var/lib/jenkins/.m2/repository/com/google/gms/google-services/4.0.1/google-services-4.0.1.pom
14:05:31 - file:/var/lib/jenkins/.m2/repository/com/google/gms/google-services/4.0.1/google-services-4.0.1.jar
14:05:31 -
14:05:31 -
14:05:31 -
14:05:31 -
14:05:31 -
14:05:31 -
je...@google.com <je...@google.com>
ha...@gmail.com <ha...@gmail.com> #10
google-servies:4.2.0 is back but firebase-plugins:1.1.5 is still missing.
ll...@gmail.com <ll...@gmail.com> #11
hello. google services dependency is fixed. but now getting these broken dependencies too:
> Could not find com.google.ads.mediation:mopub:4.15.0.0.
Searched in the following locations:
Could not find com.google.ads.interactivemedia.v3:interactivemedia:3.6.0.
Searched in the following locations:
> Could not find com.google.ads.mediation:mopub:4.15.0.0.
Searched in the following locations:
Could not find com.google.ads.interactivemedia.v3:interactivemedia:3.6.0.
Searched in the following locations:
gl...@fitbit.com <gl...@fitbit.com> #12
Also com.google.android:flexbox:0.2.6 (and com.google.android:flexbox:1.0.0)
ju...@braze.com <ju...@braze.com> #13
I think the larger developer community would appreciate an estimate or status report here.
ka...@gmail.com <ka...@gmail.com> #14
Yes a lot of man hours has gone into trying to figure this out. Their should be some better communication from the Android team when this happens.
lo...@gmail.com <lo...@gmail.com> #15
Or at least have some QA tests in place for such changes?
ag...@gmail.com <ag...@gmail.com> #16
Still not fixed completely
[21:49:48][Step 1/2] * What went wrong:
[21:49:48][Step 1/2] Could not resolve all files for configuration ':app:devDebugCompileClasspath'.
[21:49:48][Step 1/2] > Could not find com.google.android:flexbox:0.2.7.
[21:49:48][Step 1/2] Searched in the following locations:
[21:49:48][Step 1/2] file:/opt/android-sdk/extras/m2repository/com/google/android/flexbox/0.2.7/flexbox-0.2.7.pom
[21:49:48][Step 1/2] file:/opt/android-sdk/extras/m2repository/com/google/android/flexbox/0.2.7/flexbox-0.2.7.jar
[21:49:48][Step 1/2] file:/opt/android-sdk/extras/google/m2repository/com/google/android/flexbox/0.2.7/flexbox-0.2.7.pom
[21:49:48][Step 1/2] file:/opt/android-sdk/extras/google/m2repository/com/google/android/flexbox/0.2.7/flexbox-0.2.7.jar
[21:49:48][Step 1/2] file:/opt/android-sdk/extras/android/m2repository/com/google/android/flexbox/0.2.7/flexbox-0.2.7.pom
[21:49:48][Step 1/2] file:/opt/android-sdk/extras/android/m2repository/com/google/android/flexbox/0.2.7/flexbox-0.2.7.jar
[21:49:48][Step 1/2]https://dl.google.com/dl/android/maven2/com/google/android/flexbox/0.2.7/flexbox-0.2.7.pom
[21:49:48][Step 1/2]https://dl.google.com/dl/android/maven2/com/google/android/flexbox/0.2.7/flexbox-0.2.7.jar
[21:49:48][Step 1/2] 1 actionable task: 1 executed
[21:49:48][Step 1/2]https://jcenter.bintray.com/com/google/android/flexbox/0.2.7/flexbox-0.2.7.pom
[21:49:48][Step 1/2]https://jcenter.bintray.com/com/google/android/flexbox/0.2.7/flexbox-0.2.7.jar
[21:49:48][Step 1/2]https://jitpack.io/com/google/android/flexbox/0.2.7/flexbox-0.2.7.pom
[21:49:48][Step 1/2]https://jitpack.io/com/google/android/flexbox/0.2.7/flexbox-0.2.7.jar
[21:49:48][Step 1/2]https://dl.bintray.com/android/android-tools/com/google/android/flexbox/0.2.7/flexbox-0.2.7.pom
[21:49:48][Step 1/2]https://dl.bintray.com/android/android-tools/com/google/android/flexbox/0.2.7/flexbox-0.2.7.jar
[21:49:48][Step 1/2] Required by:
[21:49:48][Step 1/2] project :app
[21:49:48][Step 1/2]
[21:49:48][Step 1/2] * Try:
[21:49:48][Step 1/2] * What went wrong:
[21:49:48][Step 1/2] Could not resolve all files for configuration ':app:devDebugCompileClasspath'.
[21:49:48][Step 1/2] > Could not find com.google.android:flexbox:0.2.7.
[21:49:48][Step 1/2] Searched in the following locations:
[21:49:48][Step 1/2] file:/opt/android-sdk/extras/m2repository/com/google/android/flexbox/0.2.7/flexbox-0.2.7.pom
[21:49:48][Step 1/2] file:/opt/android-sdk/extras/m2repository/com/google/android/flexbox/0.2.7/flexbox-0.2.7.jar
[21:49:48][Step 1/2] file:/opt/android-sdk/extras/google/m2repository/com/google/android/flexbox/0.2.7/flexbox-0.2.7.pom
[21:49:48][Step 1/2] file:/opt/android-sdk/extras/google/m2repository/com/google/android/flexbox/0.2.7/flexbox-0.2.7.jar
[21:49:48][Step 1/2] file:/opt/android-sdk/extras/android/m2repository/com/google/android/flexbox/0.2.7/flexbox-0.2.7.pom
[21:49:48][Step 1/2] file:/opt/android-sdk/extras/android/m2repository/com/google/android/flexbox/0.2.7/flexbox-0.2.7.jar
[21:49:48][Step 1/2]
[21:49:48][Step 1/2]
[21:49:48][Step 1/2] 1 actionable task: 1 executed
[21:49:48][Step 1/2]
[21:49:48][Step 1/2]
[21:49:48][Step 1/2]
[21:49:48][Step 1/2]
[21:49:48][Step 1/2]
[21:49:48][Step 1/2]
[21:49:48][Step 1/2] Required by:
[21:49:48][Step 1/2] project :app
[21:49:48][Step 1/2]
[21:49:48][Step 1/2] * Try:
co...@gmail.com <co...@gmail.com> #17
Any updates on firebase-plugins:1.1.5 ? I'm still not able to build
[Deleted User] <[Deleted User]> #18
or any ETA though?
coz if this is likely gonna be fixed in the next day or two, then we can wait, otherwise will have to go with some temporary hack solutions
coz if this is likely gonna be fixed in the next day or two, then we can wait, otherwise will have to go with some temporary hack solutions
ul...@gmail.com <ul...@gmail.com> #19
`com.google.android.exoplayer:exoplayer:2.X.X` doesn't work as well.
ku...@gmail.com <ku...@gmail.com> #20
So I got a tweet from bintray claiming that it was Google that asked them to pull the binaries:
https://twitter.com/geeky_android/status/1072276765404487680?s=19
This is interesting and worrying...
This is interesting and worrying...
ba...@jfrog.com <ba...@jfrog.com> #21
Bintray used to provide those binaries as a convenience for the users (fewer repos to configure). Once Google asked JFrog not to do that, you have to use Google repos to retrieve Google artifacts.
be...@gmail.com <be...@gmail.com> #22
What a silly decision on Google's part. Hopefully this is resolved soon.
ku...@gmail.com <ku...@gmail.com> #23
I am not worried by what Bintray did here. If Google asks you to stop serving their binaries, you do it (Google had a good reason to ask imho as well but that's besides the point).
It is severely irresponsible to pull binaries out of a central repo that everyone uses without a) giving them a big heads up and b) proving a seamless alternative.
In terms of a) Google did this without letting anyone know so they could plan ahead.
As far as b) is concerned, some of the artifacts they pulled form JCenter are not even provided via google()! ExoPlayer was the one which bit us. We have to manually add exoplayer's bintray in our repos.
This was handled VERY poorly and cost hundreds of project maintainers around the world precious time troubleshooting chasing down the root of this.
This is time and money wasted that won't be taken back.
I'm surprised at the unprofessionalism with this whole affair.
It is severely irresponsible to pull binaries out of a central repo that everyone uses without a) giving them a big heads up and b) proving a seamless alternative.
In terms of a) Google did this without letting anyone know so they could plan ahead.
As far as b) is concerned, some of the artifacts they pulled form JCenter are not even provided via google()! ExoPlayer was the one which bit us. We have to manually add exoplayer's bintray in our repos.
This was handled VERY poorly and cost hundreds of project maintainers around the world precious time troubleshooting chasing down the root of this.
This is time and money wasted that won't be taken back.
I'm surprised at the unprofessionalism with this whole affair.
st...@google.com <st...@google.com> #24
The error appears to be that a number of plugins hosted on bintray are not visible in the jcenter repo. While this issue is resolved, there is a workaround (already mentioned in Comment #3 ):
If your build cannot locate a package, try to find the package on Bintray (starting points:https://bintray.com/google , https://bintray.com/firebase , or https://bintray.com/android ).
Then, add a corresponding link to the appropriate `repositories {}` block in your build.gradle file:
E.g.: if you see the error "Could not find com.google.firebase:firebase-plugins:1.1.5.", you can update your build.gradle to include:
```
repositories {
// [Other repositories...]
maven { url 'https://dl.bintray.com/firebase/gradle/ ' }
}
```
Further specific examples:
'com.google.android:flexbox:0.2.7' can be located via "maven { url 'https://dl.bintray.com/google/flexbox-layout/ ' }"
'com.google.android.exoplayer:+' can be located via "maven { url 'https://dl.bintray.com/google/exoplayer/ ' }"
'com.google.ads.mediation:mopub:4.15.0.0' can be located via "maven { url 'https://dl.bintray.com/google/mobile-ads-adapters-android/ ' }"
'com.google.ads.interactivemedia.v3:interactivemedia:3.6.0' can be located via "maven { url 'https://dl.bintray.com/google/interactivemedia/ ' }"
If your build cannot locate a package, try to find the package on Bintray (starting points:
Then, add a corresponding link to the appropriate `repositories {}` block in your build.gradle file:
E.g.: if you see the error "Could not find com.google.firebase:firebase-plugins:1.1.5.", you can update your build.gradle to include:
```
repositories {
// [Other repositories...]
maven { url '
}
```
Further specific examples:
'com.google.android:flexbox:0.2.7' can be located via "maven { url '
'com.google.android.exoplayer:+' can be located via "maven { url '
'com.google.ads.mediation:mopub:4.15.0.0' can be located via "maven { url '
'com.google.ads.interactivemedia.v3:interactivemedia:3.6.0' can be located via "maven { url '
ku...@gmail.com <ku...@gmail.com> #25
This is NOT an acceptable solution from a multibillion dollar company.
This is a workaround.
What are the plans and timelines in getting all the repos that are missing from google() into that repository?
You can't expect hundreds or thousands of project maintainers around the world to scramble around trying to fix their builds like that.
Bintray here says that Google asked them to pull the binaries from JCenter. The comment above implies that they will return to JCenter?
Which one is it?
If they don't make it to JCenter, will they make it to google()?
This is a workaround.
What are the plans and timelines in getting all the repos that are missing from google() into that repository?
You can't expect hundreds or thousands of project maintainers around the world to scramble around trying to fix their builds like that.
Bintray here says that Google asked them to pull the binaries from JCenter. The comment above implies that they will return to JCenter?
Which one is it?
If they don't make it to JCenter, will they make it to google()?
be...@gmail.com <be...@gmail.com> #26
Those of us that use Expo with React Native have no control over the repository settings, as that part of the build occurs within the platform (to Expo's credit they were quick to resolve this). That being the case, workarounds of this nature aren't viable for a subset of end-users.
If you're going to insist that mirrors be taken down, it's worth making sure your own dependency delivery is bulletproof.
If you're going to insist that mirrors be taken down, it's worth making sure your own dependency delivery is bulletproof.
sa...@google.com <sa...@google.com> #27
Hey everyone,
We understand this is a really painful situation right now for a lot of developers. Removing packages from jCenter which are not replicated in Google's maven repo was an accident and a product of a miscommunication! We're working on getting everything back into place.
Please try and be patient with us and let's try and reserve comments on this thread for updates on the situation. If you're affected by this issue and want to be heard, please click "Me too!" at the top of the page as a way of 'upvoting' this issue.
- Sam
We understand this is a really painful situation right now for a lot of developers. Removing packages from jCenter which are not replicated in Google's maven repo was an accident and a product of a miscommunication! We're working on getting everything back into place.
Please try and be patient with us and let's try and reserve comments on this thread for updates on the situation. If you're affected by this issue and want to be heard, please click "Me too!" at the top of the page as a way of 'upvoting' this issue.
- Sam
gl...@fitbit.com <gl...@fitbit.com> #28
@sam Is there any sort of (even very rough ETA)? Next few hours, next day or two, next week?
Even something that is in no way guaranteed - just a "we hope it's resolved by.."? :) . This is a frustrating situation for everyone involved, and it's be great to have some sort of idea of if we need to add in the work-arounds or if it's going to be possible to wait for the correct resolution.
Thanks!
Even something that is in no way guaranteed - just a "we hope it's resolved by.."? :) . This is a frustrating situation for everyone involved, and it's be great to have some sort of idea of if we need to add in the work-arounds or if it's going to be possible to wait for the correct resolution.
Thanks!
do...@gmail.com <do...@gmail.com> #29
Is it possible to roll back the changes? I have a few developers that can't build the project! Any workaround?
st...@google.com <st...@google.com>
sa...@google.com <sa...@google.com> #30
Hello again everyone,
We now know what happened, and are working on rolling it back in a sensible way. Here's a basic outline of the problem:
1. There were some bogus/malformed com.google.* and com.android.* artifacts on jCenter
2. Most of these artifacts were properly hosted onmaven.google.com (aka google())
3. If your build system found the jCenter version before it found the Google Maven version, your build would break
4. Google noticed this and asked jFrog to remove basically everything under com.google.* and com.android.* because we assumed it was all on Google Maven as well
5. We were wrong :-(
6. Some artifacts deleted from jCenter are causing errors in your builds
We are working on doing a few things:
* Some libraries that were deleted are being pushed to Google Maven. This includes the com.google.gms:google-services plugin, the firebase performance plugin, and Exoplayer. Try adding google() to your buildscript and app repositories blocks to see if that helps. We expect this to help many people, but not everyone.
* We are working to make a list of which libraries were improperly deleted. Some of the things deleted in step #4 above were done for good reason, so we don't want to restore those as well.
As I said before, we hate that we broke your builds and we appreciate your patience while we fix it!
- Sam
We now know what happened, and are working on rolling it back in a sensible way. Here's a basic outline of the problem:
1. There were some bogus/malformed com.google.* and com.android.* artifacts on jCenter
2. Most of these artifacts were properly hosted on
3. If your build system found the jCenter version before it found the Google Maven version, your build would break
4. Google noticed this and asked jFrog to remove basically everything under com.google.* and com.android.* because we assumed it was all on Google Maven as well
5. We were wrong :-(
6. Some artifacts deleted from jCenter are causing errors in your builds
We are working on doing a few things:
* Some libraries that were deleted are being pushed to Google Maven. This includes the com.google.gms:google-services plugin, the firebase performance plugin, and Exoplayer. Try adding google() to your buildscript and app repositories blocks to see if that helps. We expect this to help many people, but not everyone.
* We are working to make a list of which libraries were improperly deleted. Some of the things deleted in step #4 above were done for good reason, so we don't want to restore those as well.
As I said before, we hate that we broke your builds and we appreciate your patience while we fix it!
- Sam
sa...@google.com <sa...@google.com> #31
The com.google.gms:google-services plugin has been restored to jCenter (as you can see via the link below)
https://jcenter.bintray.com/com/google/gms/google-services/
r....@applicaster.com <r....@applicaster.com> #32
Hi Sam,
Do you have any updates regarding the other libraries?
Do you have any updates regarding the other libraries?
de...@gmail.com <de...@gmail.com> #33
Is the below error is due to the same issue
A problem occurred configuring project ':react-native-firebase'.
> Could not resolve all artifacts for configuration ':react-native-firebase:classpath'.
> Could not find com.android.tools.build:gradle:2.3.3.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/2.3.3/gradle-2.3.3.pom
https://jcenter.bintray.com/com/android/tools/build/gradle/2.3.3/gradle-2.3.3.jar
Required by:
project :react-native-firebase
A problem occurred configuring project ':react-native-firebase'.
> Could not resolve all artifacts for configuration ':react-native-firebase:classpath'.
> Could not find com.android.tools.build:gradle:2.3.3.
Searched in the following locations:
Required by:
project :react-native-firebase
lu...@gmail.com <lu...@gmail.com> #34
Yeah, It looks like `com.android.tools.build:gradle:2.3.3` is hosted nowhere at the moment
tr...@google.com <tr...@google.com> #35
We're still working with jCenter to restore the remaining missing packages. We'll continue to provide updates here as they become available.
tr...@google.com <tr...@google.com> #36
### STATUS ###
- The Google Services library (com.google.gms:google-services) library has been restored, see update #31.
- Requests have been submitted to jCenter to re-publish all repositories hosted onbintray.com/google . The jCenter admins at JFrog are working to get them back online for us, at this point all we can do is wait. We expect them to come online soon. Some libraries are already back.
- Some Android/Firebase libraries that were dual-homed on bothjcenter.bintray.com and maven.google.com are missing older versions (previously hosted on jCenter). We're still working at getting these back online in either jcenter.bintray.com or maven.google.com , as appropriate -- we're working carefully here to avoid re-creating the initial conflicts that caused problems. Work is ongoing. Newer versions of these libraries are unaffected, as they're available on maven.google.com .
### WORKAROUNDS ###
1. For the Google Services library, no workaround is necessary. This library is already restored. Other libraries in /google are in the progress of being restored as well.
2. For projects served frombintray.com/android or bintray.com/firebase that are not resolving, consider upgrading to a newer version that is already hosted on maven.google.com . (See below if this is not feasible.)
3. For projects frombintray.com/google , or if you are unable to upgrade to a newer version of a Android or Firebase library...you will need to temporarily add a block similar to the following to your build.gradle:
repositories {
maven {
url "https://google.bintray.com/$(REPOSITORY) "
}
}
Replace $(REPOSITORY) with the project name fromhttps://bintray.com/google .
Forbintray.com/firebase , use "https://firebase.bintray.com/$(REPOSITORY) ". For bintray.com/android , use "https://dl.bintray.com/android/$(REPOSITORY) ".
Again, this workaround is only temporary until we can get all versions either re-listed in jCenter or mirrored intomaven.google.com .
### INVESTIGATION ###
The request submitted to de-list projects from jCenter appears to have been overly broad, and was submitted by another team at Google that did not have full authority to make that change. The repository admins at Google were not consulted before this request was executed by jCenter. We'll be looking into this more in the days to come, right now our first priority is in restoring access to all versions of affected libraries.
Additionally, it appears that there may be a misconfiguration in Google's repository that is preventing mirroring frommaven.google.com into jCenter, which in turn was the cause of the initial takedown request. Correcting this misconfiguration may have avoided the need to remove anything. Additional followup is occurring internally.
- The Google Services library (com.google.gms:google-services) library has been restored, see update #31.
- Requests have been submitted to jCenter to re-publish all repositories hosted on
- Some Android/Firebase libraries that were dual-homed on both
### WORKAROUNDS ###
1. For the Google Services library, no workaround is necessary. This library is already restored. Other libraries in /google are in the progress of being restored as well.
2. For projects served from
3. For projects from
repositories {
maven {
url "
}
}
Replace $(REPOSITORY) with the project name from
For
Again, this workaround is only temporary until we can get all versions either re-listed in jCenter or mirrored into
### INVESTIGATION ###
The request submitted to de-list projects from jCenter appears to have been overly broad, and was submitted by another team at Google that did not have full authority to make that change. The repository admins at Google were not consulted before this request was executed by jCenter. We'll be looking into this more in the days to come, right now our first priority is in restoring access to all versions of affected libraries.
Additionally, it appears that there may be a misconfiguration in Google's repository that is preventing mirroring from
[Deleted User] <[Deleted User]> #37
Same here!
We're using flexbox library and exoplayer.
But we can't download these libraries from jCenter.
We're using flexbox library and exoplayer.
But we can't download these libraries from jCenter.
kr...@gmail.com <kr...@gmail.com> #38
Issue still exists.
Why there is no channel/website that tells the status of a service? That'd the first site that devs can go to and checks if something's wrong on repo side, instead wasting time trying to figure out what they did wrong.
Why there is no channel/website that tells the status of a service? That'd the first site that devs can go to and checks if something's wrong on repo side, instead wasting time trying to figure out what they did wrong.
tr...@gmail.com <tr...@gmail.com> #39
Could not find firebase-plugins.jar (com.google.firebase:firebase-plugins:1.1.5).
Searched in the following locations:
https://jcenter.bintray.com/com/google/firebase/firebase-plugins/1.1.5/firebase-plugins-1.1.5.jar
I am still struggling with this
Searched in the following locations:
I am still struggling with this
ka...@gmail.com <ka...@gmail.com> #40
Issue is still the same for 4.1.0:
> Could not find google-services.jar (com.google.gms:google-services:4.1.0).
Searched in the following locations:
https://jcenter.bintray.com/com/google/gms/google-services/4.1.0/google-services-4.1.0.jar
> Could not find google-services.jar (com.google.gms:google-services:4.1.0).
Searched in the following locations:
[Deleted User] <[Deleted User]> #41
Status of the binaries?
ak...@gmail.com <ak...@gmail.com> #42
I am facing the same issue..flexbox, exoplayer, mediation cannot be resolved
kr...@gmail.com <kr...@gmail.com> #44
To anyone having this issue:
We have to wait until artifacts will be uploaded again.
In meantime, use workaround provided by google.
For example, having problem with `android/tools`, use this:
maven {
artifactUrls "https://dl.bintray.com/android/android-tools/ "
url "https://jcenter.bintray.com "
}
We have to wait until artifacts will be uploaded again.
In meantime, use workaround provided by google.
For example, having problem with `android/tools`, use this:
maven {
artifactUrls "
url "
}
km...@gmail.com <km...@gmail.com> #45
Perhaps after things are more or less back to normal with the current mess-up - Google should start publishing their artifacts (from all teams / divisions / projects) to google() repository?
exoplayer, flexbox, gsom / json-simple, protobuf, guava, maybe others I'm missing?
It might require some communication internally (to get permissions / access) but that should be doable inside one and same company right?
exoplayer, flexbox, gsom / json-simple, protobuf, guava, maybe others I'm missing?
It might require some communication internally (to get permissions / access) but that should be doable inside one and same company right?
pa...@gmail.com <pa...@gmail.com> #46
There are still missing dependencies...
A problem occurred configuring root project 'android'.
> Could not resolve all files for configuration ':classpath'.
> Could not find gradle.jar (com.android.tools.build:gradle:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.jar
> Could not find gradle-core.jar (com.android.tools.build:gradle-core:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle-core/2.2.3/gradle-core-2.2.3.jar
> Could not find builder.jar (com.android.tools.build:builder:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/builder/2.2.3/builder-2.2.3.jar
> Could not find lint.jar (com.android.tools.lint:lint:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/lint/lint/25.2.3/lint-25.2.3.jar
> Could not find gradle-api.jar (com.android.tools.build:gradle-api:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle-api/2.2.3/gradle-api-2.2.3.jar
> Could not find compilerCommon.jar (com.android.databinding:compilerCommon:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/databinding/compilerCommon/2.2.3/compilerCommon-2.2.3.jar
> Could not find builder-model.jar (com.android.tools.build:builder-model:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/builder-model/2.2.3/builder-model-2.2.3.jar
> Could not find builder-test-api.jar (com.android.tools.build:builder-test-api:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/builder-test-api/2.2.3/builder-test-api-2.2.3.jar
> Could not find sdklib.jar (com.android.tools:sdklib:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/sdklib/25.2.3/sdklib-25.2.3.jar
> Could not find sdk-common.jar (com.android.tools:sdk-common:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/sdk-common/25.2.3/sdk-common-25.2.3.jar
> Could not find common.jar (com.android.tools:common:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/common/25.2.3/common-25.2.3.jar
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/manifest-merger/25.2.3/manifest-merger-25.2.3.jar
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/ddms/ddmlib/25.2.3/ddmlib-25.2.3.jar
> Could not find protos.jar (com.android.tools.analytics-library:protos:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/analytics-library/protos/25.2.3/protos-25.2.3.jar
> Could not find shared.jar (com.android.tools.analytics-library:shared:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/analytics-library/shared/25.2.3/shared-25.2.3.jar
> Could not find tracker.jar (com.android.tools.analytics-library:tracker:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/analytics-library/tracker/25.2.3/tracker-25.2.3.jar
> Could not find lint-checks.jar (com.android.tools.lint:lint-checks:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/lint/lint-checks/25.2.3/lint-checks-25.2.3.jar
> Could not find baseLibrary.jar (com.android.databinding:baseLibrary:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.jar
> Could not find layoutlib-api.jar (com.android.tools.layoutlib:layoutlib-api:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/layoutlib/layoutlib-api/25.2.3/layoutlib-api-25.2.3.jar
> Could not find dvlib.jar (com.android.tools:dvlib:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/dvlib/25.2.3/dvlib-25.2.3.jar
> Could not find repository.jar (com.android.tools:repository:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/repository/25.2.3/repository-25.2.3.jar
> Could not find lint-api.jar (com.android.tools.lint:lint-api:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/lint/lint-api/25.2.3/lint-api-25.2.3.jar
> Could not find annotations.jar (com.android.tools:annotations:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/annotations/25.2.3/annotations-25.2.3.jar
A problem occurred configuring root project 'android'.
> Could not resolve all files for configuration ':classpath'.
> Could not find gradle.jar (com.android.tools.build:gradle:2.2.3).
Searched in the following locations:
> Could not find gradle-core.jar (com.android.tools.build:gradle-core:2.2.3).
Searched in the following locations:
> Could not find builder.jar (com.android.tools.build:builder:2.2.3).
Searched in the following locations:
> Could not find lint.jar (com.android.tools.lint:lint:25.2.3).
Searched in the following locations:
> Could not find gradle-api.jar (com.android.tools.build:gradle-api:2.2.3).
Searched in the following locations:
> Could not find compilerCommon.jar (com.android.databinding:compilerCommon:2.2.3).
Searched in the following locations:
> Could not find builder-model.jar (com.android.tools.build:builder-model:2.2.3).
Searched in the following locations:
> Could not find builder-test-api.jar (com.android.tools.build:builder-test-api:2.2.3).
Searched in the following locations:
> Could not find sdklib.jar (com.android.tools:sdklib:25.2.3).
Searched in the following locations:
> Could not find sdk-common.jar (com.android.tools:sdk-common:25.2.3).
Searched in the following locations:
> Could not find common.jar (com.android.tools:common:25.2.3).
Searched in the following locations:
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:25.2.3).
Searched in the following locations:
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:25.2.3).
Searched in the following locations:
> Could not find protos.jar (com.android.tools.analytics-library:protos:25.2.3).
Searched in the following locations:
> Could not find shared.jar (com.android.tools.analytics-library:shared:25.2.3).
Searched in the following locations:
> Could not find tracker.jar (com.android.tools.analytics-library:tracker:25.2.3).
Searched in the following locations:
> Could not find lint-checks.jar (com.android.tools.lint:lint-checks:25.2.3).
Searched in the following locations:
> Could not find baseLibrary.jar (com.android.databinding:baseLibrary:2.2.3).
Searched in the following locations:
> Could not find layoutlib-api.jar (com.android.tools.layoutlib:layoutlib-api:25.2.3).
Searched in the following locations:
> Could not find dvlib.jar (com.android.tools:dvlib:25.2.3).
Searched in the following locations:
> Could not find repository.jar (com.android.tools:repository:25.2.3).
Searched in the following locations:
> Could not find lint-api.jar (com.android.tools.lint:lint-api:25.2.3).
Searched in the following locations:
> Could not find annotations.jar (com.android.tools:annotations:25.2.3).
Searched in the following locations:
ga...@gmail.com <ga...@gmail.com> #47
CI are failing:
Could not find com.google.android:flexbox:1.0.0.
https://jcenter.bintray.com/com/google/android/flexbox/1.0.0/flexbox-1.0.0.pom
https://jcenter.bintray.com/com/google/android/flexbox/1.0.0/flexbox-1.0.0.jar
https://dl.google.com/dl/android/maven2/com/google/android/flexbox/1.0.0/flexbox-1.0.0.pom
https://dl.google.com/dl/android/maven2/com/google/android/flexbox/1.0.0/flexbox-1.0.0.jar
https://repo.maven.apache.org/maven2/com/google/android/flexbox/1.0.0/flexbox-1.0.0.pom
https://repo.maven.apache.org/maven2/com/google/android/flexbox/1.0.0/flexbox-1.0.0.jar
https://jitpack.io/com/google/android/flexbox/1.0.0/flexbox-1.0.0.pom
https://jitpack.io/com/google/android/flexbox/1.0.0/flexbox-1.0.0.jar
https://maven.fabric.io/public/com/google/android/flexbox/1.0.0/flexbox-1.0.0.pom
https://maven.fabric.io/public/com/google/android/flexbox/1.0.0/flexbox-1.0.0.jar
https://dl.bintray.com/drummer-aidan/maven/com/google/android/flexbox/1.0.0/flexbox-1.0.0.pom
https://dl.bintray.com/drummer-aidan/maven/com/google/android/flexbox/1.0.0/flexbox-1.0.0.jar
Could not find com.android.databinding:baseLibrary:2.2.3.
https://jcenter.bintray.com/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.pom
https://jcenter.bintray.com/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.jar
https://dl.google.com/dl/android/maven2/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.pom
https://dl.google.com/dl/android/maven2/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.jar
https://repo.maven.apache.org/maven2/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.pom
https://repo.maven.apache.org/maven2/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.jar
https://jitpack.io/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.pom
https://jitpack.io/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.jar
https://maven.fabric.io/public/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.pom
https://maven.fabric.io/public/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.jar
https://dl.bintray.com/drummer-aidan/maven/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.pom
https://dl.bintray.com/drummer-aidan/maven/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.jar
Could not find com.google.android.exoplayer:exoplayer-smoothstreaming:2.9.1.
https://jcenter.bintray.com/com/google/android/exoplayer/exoplayer-smoothstreaming/2.9.1/exoplayer-smoothstreaming-2.9.1.pom
https://jcenter.bintray.com/com/google/android/exoplayer/exoplayer-smoothstreaming/2.9.1/exoplayer-smoothstreaming-2.9.1.jar
https://dl.google.com/dl/android/maven2/com/google/android/exoplayer/exoplayer-smoothstreaming/2.9.1/exoplayer-smoothstreaming-2.9.1.pom
https://dl.google.com/dl/android/maven2/com/google/android/exoplayer/exoplayer-smoothstreaming/2.9.1/exoplayer-smoothstreaming-2.9.1.jar
https://repo.maven.apache.org/maven2/com/google/android/exoplayer/exoplayer-smoothstreaming/2.9.1/exoplayer-smoothstreaming-2.9.1.pom
https://repo.maven.apache.org/maven2/com/google/android/exoplayer/exoplayer-smoothstreaming/2.9.1/exoplayer-smoothstreaming-2.9.1.jar
https://jitpack.io/com/google/android/exoplayer/exoplayer-smoothstreaming/2.9.1/exoplayer-smoothstreaming-2.9.1.pom
https://jitpack.io/com/google/android/exoplayer/exoplayer-smoothstreaming/2.9.1/exoplayer-smoothstreaming-2.9.1.jar
https://maven.fabric.io/public/com/google/android/exoplayer/exoplayer-smoothstreaming/2.9.1/exoplayer-smoothstreaming-2.9.1.pom
https://maven.fabric.io/public/com/google/android/exoplayer/exoplayer-smoothstreaming/2.9.1/exoplayer-smoothstreaming-2.9.1.jar
https://dl.bintray.com/drummer-aidan/maven/com/google/android/exoplayer/exoplayer-smoothstreaming/2.9.1/exoplayer-smoothstreaming-2.9.1.pom
https://dl.bintray.com/drummer-aidan/maven/com/google/android/exoplayer/exoplayer-smoothstreaming/2.9.1/exoplayer-smoothstreaming-2.9.1.jar
Could not find com.google.android:flexbox:1.0.0.
Could not find com.android.databinding:baseLibrary:2.2.3.
Could not find com.google.android.exoplayer:exoplayer-smoothstreaming:2.9.1.
[Deleted User] <[Deleted User]> #48
I am still stuck on this:
* What went wrong:
> Could not find any matches for com.android.tools.build:gradle:2.3.+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml
https://jcenter.bintray.com/com/android/tools/build/gradle/
* What went wrong:
> Could not find any matches for com.android.tools.build:gradle:2.3.+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
ja...@gmail.com <ja...@gmail.com> #49
Same here for recyclerview-v7 and Google repository:
Could not resolve all files for configuration ':app:debugCompileClasspath'.
> Could not find recyclerview-v7.jar (com.android.support:recyclerview-v7:28.0.0).
Searched in the following locations:
https://dl.google.com/dl/android/maven2/com/android/support/recyclerview-v7/28.0.0/recyclerview-v7-28.0.0.jar
Could not resolve all files for configuration ':app:debugCompileClasspath'.
> Could not find recyclerview-v7.jar (com.android.support:recyclerview-v7:28.0.0).
Searched in the following locations:
ka...@gmail.com <ka...@gmail.com> #50
Also these:
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.1).
Searched in the following locations:
https://plugins.gradle.org/m2/com/android/tools/build/manifest-merger/26.0.1/manifest-merger-26.0.1.jar
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:26.0.1).
Searched in the following locations:
https://plugins.gradle.org/m2/com/android/tools/ddms/ddmlib/26.0.1/ddmlib-26.0.1.jar
> Could not find dvlib.jar (com.android.tools:dvlib:26.0.1).
Searched in the following locations:
https://plugins.gradle.org/m2/com/android/tools/dvlib/26.0.1/dvlib-26.0.1.jar
> Could not find common.jar (com.android.tools:common:26.0.1).
Searched in the following locations:
https://plugins.gradle.org/m2/com/android/tools/common/26.0.1/common-26.0.1.jar
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.1).
Searched in the following locations:
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:26.0.1).
Searched in the following locations:
> Could not find dvlib.jar (com.android.tools:dvlib:26.0.1).
Searched in the following locations:
> Could not find common.jar (com.android.tools:common:26.0.1).
Searched in the following locations:
pa...@gmail.com <pa...@gmail.com> #51
Is there an estimate to completely fix this problem? There are a lot of missing libraries...
ra...@gmail.com <ra...@gmail.com> #52
Getting this issue:
Could not find any matches for com.android.tools.build:gradle:2.3.+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml
https://jcenter.bintray.com/com/android/tools/build/gradle/
Required by:
pastavia:react-native-vector-icons:unspecified
Could not find any matches for com.android.tools.build:gradle:2.3.+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
Required by:
pastavia:react-native-vector-icons:unspecified
ja...@gmail.com <ja...@gmail.com> #53
We are getting the same as the issue above ^^
ma...@gmail.com <ma...@gmail.com> #54
same here ;)
sh...@gmail.com <sh...@gmail.com> #55
Same here. Had to use the work arounds but we need an official fix.
ma...@gmail.com <ma...@gmail.com> #56
I've been having the same problem since yesterday:
> Could not resolve all files for configuration 'classpath'.
> Could not find any matches for com.android.tools.build:gradle:2.3.+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml
https://jcenter.bintray.com/com/android/tools/build/gradle/
> Could not resolve all files for configuration 'classpath'.
> Could not find any matches for com.android.tools.build:gradle:2.3.+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
pa...@gmail.com <pa...@gmail.com> #57
I've tried every workaround mentioned both here and in stackoverflow and nothing works...
I'm still getting the following errors..
BUILD FAILED
Total time: 0.551 secs
/home/patricio/infomigra_app/platforms/android/gradlew: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'android'.
> Could not resolve all files for configuration ':classpath'.
> Could not find gradle.jar (com.android.tools.build:gradle:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.jar
> Could not find gradle-core.jar (com.android.tools.build:gradle-core:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle-core/2.2.3/gradle-core-2.2.3.jar
> Could not find builder.jar (com.android.tools.build:builder:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/builder/2.2.3/builder-2.2.3.jar
> Could not find lint.jar (com.android.tools.lint:lint:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/lint/lint/25.2.3/lint-25.2.3.jar
> Could not find gradle-api.jar (com.android.tools.build:gradle-api:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle-api/2.2.3/gradle-api-2.2.3.jar
> Could not find compilerCommon.jar (com.android.databinding:compilerCommon:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/databinding/compilerCommon/2.2.3/compilerCommon-2.2.3.jar
> Could not find builder-model.jar (com.android.tools.build:builder-model:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/builder-model/2.2.3/builder-model-2.2.3.jar
> Could not find builder-test-api.jar (com.android.tools.build:builder-test-api:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/builder-test-api/2.2.3/builder-test-api-2.2.3.jar
> Could not find sdklib.jar (com.android.tools:sdklib:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/sdklib/25.2.3/sdklib-25.2.3.jar
> Could not find sdk-common.jar (com.android.tools:sdk-common:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/sdk-common/25.2.3/sdk-common-25.2.3.jar
> Could not find common.jar (com.android.tools:common:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/common/25.2.3/common-25.2.3.jar
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/manifest-merger/25.2.3/manifest-merger-25.2.3.jar
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/ddms/ddmlib/25.2.3/ddmlib-25.2.3.jar
> Could not find protos.jar (com.android.tools.analytics-library:protos:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/analytics-library/protos/25.2.3/protos-25.2.3.jar
> Could not find shared.jar (com.android.tools.analytics-library:shared:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/analytics-library/shared/25.2.3/shared-25.2.3.jar
> Could not find tracker.jar (com.android.tools.analytics-library:tracker:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/analytics-library/tracker/25.2.3/tracker-25.2.3.jar
> Could not find lint-checks.jar (com.android.tools.lint:lint-checks:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/lint/lint-checks/25.2.3/lint-checks-25.2.3.jar
> Could not find baseLibrary.jar (com.android.databinding:baseLibrary:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.jar
> Could not find layoutlib-api.jar (com.android.tools.layoutlib:layoutlib-api:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/layoutlib/layoutlib-api/25.2.3/layoutlib-api-25.2.3.jar
> Could not find dvlib.jar (com.android.tools:dvlib:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/dvlib/25.2.3/dvlib-25.2.3.jar
> Could not find repository.jar (com.android.tools:repository:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/repository/25.2.3/repository-25.2.3.jar
> Could not find lint-api.jar (com.android.tools.lint:lint-api:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/lint/lint-api/25.2.3/lint-api-25.2.3.jar
> Could not find annotations.jar (com.android.tools:annotations:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/annotations/25.2.3/annotations-25.2.3.jar
I'm still getting the following errors..
BUILD FAILED
Total time: 0.551 secs
/home/patricio/infomigra_app/platforms/android/gradlew: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'android'.
> Could not resolve all files for configuration ':classpath'.
> Could not find gradle.jar (com.android.tools.build:gradle:2.2.3).
Searched in the following locations:
> Could not find gradle-core.jar (com.android.tools.build:gradle-core:2.2.3).
Searched in the following locations:
> Could not find builder.jar (com.android.tools.build:builder:2.2.3).
Searched in the following locations:
> Could not find lint.jar (com.android.tools.lint:lint:25.2.3).
Searched in the following locations:
> Could not find gradle-api.jar (com.android.tools.build:gradle-api:2.2.3).
Searched in the following locations:
> Could not find compilerCommon.jar (com.android.databinding:compilerCommon:2.2.3).
Searched in the following locations:
> Could not find builder-model.jar (com.android.tools.build:builder-model:2.2.3).
Searched in the following locations:
> Could not find builder-test-api.jar (com.android.tools.build:builder-test-api:2.2.3).
Searched in the following locations:
> Could not find sdklib.jar (com.android.tools:sdklib:25.2.3).
Searched in the following locations:
> Could not find sdk-common.jar (com.android.tools:sdk-common:25.2.3).
Searched in the following locations:
> Could not find common.jar (com.android.tools:common:25.2.3).
Searched in the following locations:
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:25.2.3).
Searched in the following locations:
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:25.2.3).
Searched in the following locations:
> Could not find protos.jar (com.android.tools.analytics-library:protos:25.2.3).
Searched in the following locations:
> Could not find shared.jar (com.android.tools.analytics-library:shared:25.2.3).
Searched in the following locations:
> Could not find tracker.jar (com.android.tools.analytics-library:tracker:25.2.3).
Searched in the following locations:
> Could not find lint-checks.jar (com.android.tools.lint:lint-checks:25.2.3).
Searched in the following locations:
> Could not find baseLibrary.jar (com.android.databinding:baseLibrary:2.2.3).
Searched in the following locations:
> Could not find layoutlib-api.jar (com.android.tools.layoutlib:layoutlib-api:25.2.3).
Searched in the following locations:
> Could not find dvlib.jar (com.android.tools:dvlib:25.2.3).
Searched in the following locations:
> Could not find repository.jar (com.android.tools:repository:25.2.3).
Searched in the following locations:
> Could not find lint-api.jar (com.android.tools.lint:lint-api:25.2.3).
Searched in the following locations:
> Could not find annotations.jar (com.android.tools:annotations:25.2.3).
Searched in the following locations:
s....@gmail.com <s....@gmail.com> #58
This is really inconvenient as we have a lot of deadlines to hit before the holiday. This is a high priority item that hasn't been addressed in 24h. Why doesn't this ticket mention this is affecting production?
sh...@gmail.com <sh...@gmail.com> #59
Could not find any matches for com.android.tools.build:gradle:+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml
https://jcenter.bintray.com/com/android/tools/build/gradle/
file:/C:/Users/Shantanu/.m2/repository/com/android/tools/build/gradle/maven-metadata.xml
file:/C:/Users/Shantanu/.m2/repository/com/android/tools/build/gradle/
Required by:
unspecified:unspecified:unspecified
Searched in the following locations:
file:/C:/Users/Shantanu/.m2/repository/com/android/tools/build/gradle/maven-metadata.xml
file:/C:/Users/Shantanu/.m2/repository/com/android/tools/build/gradle/
Required by:
unspecified:unspecified:unspecified
sh...@gmail.com <sh...@gmail.com> #60
Tried every work around mentioned until now.
de...@gmail.com <de...@gmail.com> #61
I have had 3 people report this same issue, it appears Android builds are broken entirely.
le...@gmail.com <le...@gmail.com> #62
* What went wrong:
A problem occurred configuring project ':react-native-vector-icons'.
> Could not resolve all files for configuration ':react-native-vector-icons:classpath'.
> Could not find any matches for com.android.tools.build:gradle:2.3.+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml
https://jcenter.bintray.com/com/android/tools/build/gradle/
Required by:
project :react-native-vector-icons
A problem occurred configuring project ':react-native-vector-icons'.
> Could not resolve all files for configuration ':react-native-vector-icons:classpath'.
> Could not find any matches for com.android.tools.build:gradle:2.3.+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
Required by:
project :react-native-vector-icons
ja...@gmail.com <ja...@gmail.com> #63
It's definitely affecting production for us, we are supposed to be doing a production deployment in the next 1:30
ra...@gmail.com <ra...@gmail.com> #64
This workaround works for me:
buildscript {
repositories {
jcenter()
maven {
url "https://dl.bintray.com/android/android-tools/ "
}
}
dependencies {
classpath 'com.android.tools.build:gradle:2.2.3'
}
}
allprojects {
repositories {
mavenLocal()
jcenter()
maven {
url 'https://dl.bintray.com/google/exoplayer/ '
}
}
}
subprojects { subproject ->
if (subproject.name.contains('react-native-vector-icons') ||
subproject.name.contains('react-native-image-picker') ||
subproject.name.contains('react-native-linear-gradient') ||
subproject.name.contains('rn-fetch-blob') ||
subproject.name.contains('react-native-image-resizer')){
buildscript {
repositories {
maven { url "https://dl.bintray.com/android/android-tools/ " }
}
}
}
}
buildscript {
repositories {
jcenter()
maven {
url "
}
}
dependencies {
classpath 'com.android.tools.build:gradle:2.2.3'
}
}
allprojects {
repositories {
mavenLocal()
jcenter()
maven {
url '
}
}
}
subprojects { subproject ->
if (subproject.name.contains('react-native-vector-icons') ||
subproject.name.contains('react-native-image-picker') ||
subproject.name.contains('react-native-linear-gradient') ||
subproject.name.contains('rn-fetch-blob') ||
subproject.name.contains('react-native-image-resizer')){
buildscript {
repositories {
maven { url "
}
}
}
}
de...@gmail.com <de...@gmail.com> #65
Looks like this is fixed in Cordova-Android 7.1.2 already https://github.com/apache/cordova-android/pull/523
Using phonegap-version cli-8.1.1 should have that fix
Using phonegap-version cli-8.1.1 should have that fix
pa...@gmail.com <pa...@gmail.com> #66
Still doesn't work for me
I'm still getting these errors:
BUILD FAILED
Total time: 0.618 secs
/home/patricio/infomigra_app/platforms/android/gradlew: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'android'.
> Could not resolve all files for configuration ':classpath'.
> Could not find gradle.jar (com.android.tools.build:gradle:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.jar
> Could not find gradle-core.jar (com.android.tools.build:gradle-core:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle-core/2.2.3/gradle-core-2.2.3.jar
> Could not find builder.jar (com.android.tools.build:builder:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/builder/2.2.3/builder-2.2.3.jar
> Could not find lint.jar (com.android.tools.lint:lint:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/lint/lint/25.2.3/lint-25.2.3.jar
> Could not find gradle-api.jar (com.android.tools.build:gradle-api:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle-api/2.2.3/gradle-api-2.2.3.jar
> Could not find compilerCommon.jar (com.android.databinding:compilerCommon:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/databinding/compilerCommon/2.2.3/compilerCommon-2.2.3.jar
> Could not find builder-model.jar (com.android.tools.build:builder-model:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/builder-model/2.2.3/builder-model-2.2.3.jar
> Could not find builder-test-api.jar (com.android.tools.build:builder-test-api:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/builder-test-api/2.2.3/builder-test-api-2.2.3.jar
> Could not find sdklib.jar (com.android.tools:sdklib:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/sdklib/25.2.3/sdklib-25.2.3.jar
> Could not find sdk-common.jar (com.android.tools:sdk-common:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/sdk-common/25.2.3/sdk-common-25.2.3.jar
> Could not find common.jar (com.android.tools:common:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/common/25.2.3/common-25.2.3.jar
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/manifest-merger/25.2.3/manifest-merger-25.2.3.jar
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/ddms/ddmlib/25.2.3/ddmlib-25.2.3.jar
> Could not find protos.jar (com.android.tools.analytics-library:protos:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/analytics-library/protos/25.2.3/protos-25.2.3.jar
> Could not find shared.jar (com.android.tools.analytics-library:shared:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/analytics-library/shared/25.2.3/shared-25.2.3.jar
> Could not find tracker.jar (com.android.tools.analytics-library:tracker:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/analytics-library/tracker/25.2.3/tracker-25.2.3.jar
> Could not find lint-checks.jar (com.android.tools.lint:lint-checks:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/lint/lint-checks/25.2.3/lint-checks-25.2.3.jar
> Could not find baseLibrary.jar (com.android.databinding:baseLibrary:2.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.jar
> Could not find layoutlib-api.jar (com.android.tools.layoutlib:layoutlib-api:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/layoutlib/layoutlib-api/25.2.3/layoutlib-api-25.2.3.jar
> Could not find dvlib.jar (com.android.tools:dvlib:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/dvlib/25.2.3/dvlib-25.2.3.jar
> Could not find repository.jar (com.android.tools:repository:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/repository/25.2.3/repository-25.2.3.jar
> Could not find lint-api.jar (com.android.tools.lint:lint-api:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/lint/lint-api/25.2.3/lint-api-25.2.3.jar
> Could not find annotations.jar (com.android.tools:annotations:25.2.3).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/annotations/25.2.3/annotations-25.2.3.jar
I'm still getting these errors:
BUILD FAILED
Total time: 0.618 secs
/home/patricio/infomigra_app/platforms/android/gradlew: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'android'.
> Could not resolve all files for configuration ':classpath'.
> Could not find gradle.jar (com.android.tools.build:gradle:2.2.3).
Searched in the following locations:
> Could not find gradle-core.jar (com.android.tools.build:gradle-core:2.2.3).
Searched in the following locations:
> Could not find builder.jar (com.android.tools.build:builder:2.2.3).
Searched in the following locations:
> Could not find lint.jar (com.android.tools.lint:lint:25.2.3).
Searched in the following locations:
> Could not find gradle-api.jar (com.android.tools.build:gradle-api:2.2.3).
Searched in the following locations:
> Could not find compilerCommon.jar (com.android.databinding:compilerCommon:2.2.3).
Searched in the following locations:
> Could not find builder-model.jar (com.android.tools.build:builder-model:2.2.3).
Searched in the following locations:
> Could not find builder-test-api.jar (com.android.tools.build:builder-test-api:2.2.3).
Searched in the following locations:
> Could not find sdklib.jar (com.android.tools:sdklib:25.2.3).
Searched in the following locations:
> Could not find sdk-common.jar (com.android.tools:sdk-common:25.2.3).
Searched in the following locations:
> Could not find common.jar (com.android.tools:common:25.2.3).
Searched in the following locations:
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:25.2.3).
Searched in the following locations:
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:25.2.3).
Searched in the following locations:
> Could not find protos.jar (com.android.tools.analytics-library:protos:25.2.3).
Searched in the following locations:
> Could not find shared.jar (com.android.tools.analytics-library:shared:25.2.3).
Searched in the following locations:
> Could not find tracker.jar (com.android.tools.analytics-library:tracker:25.2.3).
Searched in the following locations:
> Could not find lint-checks.jar (com.android.tools.lint:lint-checks:25.2.3).
Searched in the following locations:
> Could not find baseLibrary.jar (com.android.databinding:baseLibrary:2.2.3).
Searched in the following locations:
> Could not find layoutlib-api.jar (com.android.tools.layoutlib:layoutlib-api:25.2.3).
Searched in the following locations:
> Could not find dvlib.jar (com.android.tools:dvlib:25.2.3).
Searched in the following locations:
> Could not find repository.jar (com.android.tools:repository:25.2.3).
Searched in the following locations:
> Could not find lint-api.jar (com.android.tools.lint:lint-api:25.2.3).
Searched in the following locations:
> Could not find annotations.jar (com.android.tools:annotations:25.2.3).
Searched in the following locations:
de...@gmail.com <de...@gmail.com> #67
Ya updating to cli-8.1.1 didn't work for me either.
Where do you put this code?
buildscript {
repositories {
jcenter()
maven {
url "https://dl.bintray.com/android/android-tools/ "
}
}
dependencies {
classpath 'com.android.tools.build:gradle:2.2.3'
}
}
...
Where do you put this code?
buildscript {
repositories {
jcenter()
maven {
url "
}
}
dependencies {
classpath 'com.android.tools.build:gradle:2.2.3'
}
}
...
de...@gmail.com <de...@gmail.com> #68
^^^ Put that in the project level build.gradle file.
jj...@gmail.com <jj...@gmail.com> #69
The issue I am having with the workaround is that it does not address fixes for any dependencies within react-native projects. I can update the build.gradle in the base project, but still get errors when trying to build with any dependencies that are being built that also use that repo.
kr...@gmail.com <kr...@gmail.com> #70
It's because gradle will use whatever it has written in buildscript in its submodules - you have to change it in every submodule to get it to work
cr...@gmail.com <cr...@gmail.com> #71
^^^ I too have react native modules and was able to move the exoplayer dependency to my project level build.gradle file to fix that dependency issue. However, I still had an issue with a react native module using build tools 2.2.3. I was able to fix that issue by opening that module's gradle file and adding:
buildscript {
repositories {
maven { url 'https://dl.bintray.com/android/android-tools/ ' }
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.2.3'
}
}
Adding `maven { url 'https://dl.bintray.com/android/android-tools/ ' }` to my root project level build.gradle file didn't work. I'm not 100% why since it was listed above the jcenter() listing and I'd assume would trump it.
buildscript {
repositories {
maven { url '
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.2.3'
}
}
Adding `maven { url '
fd...@gmail.com <fd...@gmail.com> #72
Me too...
* What went wrong:
A problem occurred configuring project ':CordovaLib'.
> Could not resolve all files for configuration ':CordovaLib:classpath'.
> Could not find com.android.tools.build:gradle:2.2.3.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.pom
https://jcenter.bintray.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.jar
https://maven.google.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.pom
https://maven.google.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.jar
Required by:
project :CordovaLib
* What went wrong:
A problem occurred configuring project ':CordovaLib'.
> Could not resolve all files for configuration ':CordovaLib:classpath'.
> Could not find com.android.tools.build:gradle:2.2.3.
Searched in the following locations:
Required by:
project :CordovaLib
jj...@gmail.com <jj...@gmail.com> #73
So, to change it in every submodule seems like it would mean:
1. Find the github repo for any submodule that is broken and fork it to our own repo.
2. Changing the build.gradle in our fork'ed version to have the fix
3. Updating our yarn files to pull the module from our forked version
And then undoing this once it is fixed...
1. Find the github repo for any submodule that is broken and fork it to our own repo.
2. Changing the build.gradle in our fork'ed version to have the fix
3. Updating our yarn files to pull the module from our forked version
And then undoing this once it is fixed...
ed...@gmail.com <ed...@gmail.com> #74
I'm also getting the same error.....
* What went wrong:
A problem occurred configuring root project 'android'.
> Could not resolve all dependencies for configuration ':classpath'.
> Could not find com.android.tools.build:gradle:2.2.3.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.pom
https://jcenter.bintray.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.jar
https://maven.google.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.pom
https://maven.google.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.jar
Required by:
project :
* What went wrong:
A problem occurred configuring root project 'android'.
> Could not resolve all dependencies for configuration ':classpath'.
> Could not find com.android.tools.build:gradle:2.2.3.
Searched in the following locations:
Required by:
project :
pk...@shipt.com <pk...@shipt.com> #75
Has there been any update on the libraries that still seem to be missing? Gradle 3.2.1 is now present for me, but i am still getting the following:
> Could not find com.android.tools.build:gradle:2.2.3.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.pom
https://jcenter.bintray.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.jar
Required by:
project :react-native-blur
> Could not find com.android.tools.build:gradle:2.2.3.
Searched in the following locations:
Required by:
project :react-native-blur
di...@instacart.com <di...@instacart.com> #76
I didn't see a "Me too" button to upvote this, so I am leaving a comment.
[Deleted User] <[Deleted User]> #77
Please stop posting "Me Too" that does not contribute with the discussion.
The issue is already being worked on, it has Severity S1 and Priority P0.
You can "Star" the issue at the top to receive update notifications.
The issue is already being worked on, it has Severity S1 and Priority P0.
You can "Star" the issue at the top to receive update notifications.
jo...@gmail.com <jo...@gmail.com> #78
This affects my release (React Native / Expo app) that was planned for today.
Would be great to get an ETA on when this could be sorted out.
Is there any kind of official press release about this, so it can be communicated to the business?
* What went wrong:
A problem occurred configuring root project 'android'.
> Could not resolve all dependencies for configuration ':classpath'.
> Could not find com.android.tools.build:gradle:2.3.3.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/2.3.3/gradle-2.3.3.pom
https://jcenter.bintray.com/com/android/tools/build/gradle/2.3.3/gradle-2.3.3.jar
Would be great to get an ETA on when this could be sorted out.
Is there any kind of official press release about this, so it can be communicated to the business?
* What went wrong:
A problem occurred configuring root project 'android'.
> Could not resolve all dependencies for configuration ':classpath'.
> Could not find com.android.tools.build:gradle:2.3.3.
Searched in the following locations:
ra...@gmail.com <ra...@gmail.com> #79
When are we expecting all the libraries to up. If it is by tomorrow, we can wait else we'll point to maven to proceed with work.
pa...@gmail.com <pa...@gmail.com> #80
#MeToo
br...@gtempaccount.com <br...@gtempaccount.com> #81
For those with React Native projects, additionally adding this block of code inside your root build.gradle seems to fix the issues for us:
allprojects {
buildscript {
repositories {
google()
mavenCentral()
jcenter()
// TODO: Remove when Google fixes their issues
maven { url 'https://dl.bintray.com/android/android-tools ' }
}
}
}
NOTE: You also need to add the
"maven { url 'https://dl.bintray.com/android/android-tools ' }"
line into your normal buildscript repositories block.
For React Native library maintainers, please stop adding you own buildscript block into your own build.gradle files.
allprojects {
buildscript {
repositories {
google()
mavenCentral()
jcenter()
// TODO: Remove when Google fixes their issues
maven { url '
}
}
}
NOTE: You also need to add the
"maven { url '
line into your normal buildscript repositories block.
For React Native library maintainers, please stop adding you own buildscript block into your own build.gradle files.
um...@gmail.com <um...@gmail.com> #82
is there any workaround for cordova based apps as i have tried everything but none of it, works.
pa...@gmail.com <pa...@gmail.com> #83
I'm also working in a cordova project and I've tried every 'workaround'... but nothing works.
[Deleted User] <[Deleted User]> #84
> For React Native library maintainers, please stop adding you own buildscript block into your own build.gradle files.
Yeah, good point. This does help alleviate "dependency hell" :)
Yeah, good point. This does help alleviate "dependency hell" :)
sa...@google.com <sa...@google.com> #85
Hi again everyone,
We are continuing to work with the JFrog team to roll back as much of the deletion as possible and get these packages back on JCenter. We hope this will fix the majority of your build issues. Once we are in a more stable place, we (Google) will work on long-term improvements to our processes to make sure this does not happen again.
For those of you who are using Gradle/Android Studio to build your Android projects you can directly add dependencies on Bintray repositories as a workaround (as Trevor mentioned before). I will list a few specific examples to try and make things as clear as possible.
Note that thesedl.bintray.com repositories are officially maintained by Google and can be trusted, they are the original binary sources for the missing artifacts.
## Android Build Tools (ex: com.android.tools.build:gradle)
In your top level build.gradle file you can add the repository within the buildscript{} block like this:
buildscript {
// ...
repositories {
maven { url 'https://dl.bintray.com/android/android-tools/ ' }
// ...
// ... everything else ...
// ...
}
// ...
}
## Firebase Plugins (ex: com.google.firebase:firebase-plugins)
In your top level build.gradle file you can add the repository within the buildscript{} block like this:
buildscript {
// ...
repositories {
maven { url 'https://dl.bintray.com/firebase/gradle/ ' }
// ...
// ... everything else ...
// ...
}
// ...
}
## Exoplayer
In your app level build.gradle file you can add the repository in a repositories{} block above your dependencies{} block
android {
// ...
}
repositories {
maven { url 'https://dl.bintray.com/google/exoplayer/ ' }
// ...
// ... everything else ...
// ...
}
dependencies {
// ...
}
## Flexbox
In your app level build.gradle file you can add the repository in a repositories{} block above your dependencies{} block
android {
// ...
}
repositories {
maven { url 'https://dl.bintray.com/google/flexbox-layout/ ' }
// ...
// ... everything else ...
// ...
}
dependencies {
// ...
}
We are continuing to work with the JFrog team to roll back as much of the deletion as possible and get these packages back on JCenter. We hope this will fix the majority of your build issues. Once we are in a more stable place, we (Google) will work on long-term improvements to our processes to make sure this does not happen again.
For those of you who are using Gradle/Android Studio to build your Android projects you can directly add dependencies on Bintray repositories as a workaround (as Trevor mentioned before). I will list a few specific examples to try and make things as clear as possible.
Note that these
## Android Build Tools (ex: com.android.tools.build:gradle)
In your top level build.gradle file you can add the repository within the buildscript{} block like this:
buildscript {
// ...
repositories {
maven { url '
// ...
// ... everything else ...
// ...
}
// ...
}
## Firebase Plugins (ex: com.google.firebase:firebase-plugins)
In your top level build.gradle file you can add the repository within the buildscript{} block like this:
buildscript {
// ...
repositories {
maven { url '
// ...
// ... everything else ...
// ...
}
// ...
}
## Exoplayer
In your app level build.gradle file you can add the repository in a repositories{} block above your dependencies{} block
android {
// ...
}
repositories {
maven { url '
// ...
// ... everything else ...
// ...
}
dependencies {
// ...
}
## Flexbox
In your app level build.gradle file you can add the repository in a repositories{} block above your dependencies{} block
android {
// ...
}
repositories {
maven { url '
// ...
// ... everything else ...
// ...
}
dependencies {
// ...
}
ar...@carbonaut.io <ar...@carbonaut.io> #86
I'm still missing many libraries, or the workaround is not working properly for Cordova Apps. These are the ones I get an error when trying to build, using the workaround above:
Could not find org.ow2.asm:asm:5.0.4.
Could not find org.ow2.asm:asm-commons:5.0.4.
Could not find net.sf.proguard:proguard-gradle:5.2.1.
Could not find org.jacoco:org.jacoco.core:0.7.5.201505241946.
Could not find org.jacoco:org.jacoco.report:0.7.5.201505241946.
Could not find net.sf.jopt-simple:jopt-simple:4.9.
Could not find com.google.protobuf:protobuf-java:2.5.0.
Could not find org.antlr:antlr:3.5.2.
Could not find com.squareup:javawriter:2.5.0.
Could not find org.bouncycastle:bcpkix-jdk15on:1.48.
Could not find org.bouncycastle:bcprov-jdk15on:1.48.
Could not find org.ow2.asm:asm-tree:5.0.4.
Could not find org.eclipse.jdt.core.compiler:ecj:4.5.1.
Could not find com.google.guava:guava:18.0.
Could not find org.antlr:antlr4:4.5.3.
Could not find commons-io:commons-io:2.4.
Could not find com.googlecode.juniversalchardet:juniversalchardet:1.0.3.
Could not find com.google.code.gson:gson:2.2.4.
Could not find org.apache.commons:commons-compress:1.8.1.
Could not find org.apache.httpcomponents:httpclient:4.1.1.
Could not find org.apache.httpcomponents:httpmime:4.1.
Could not find com.google.guava:guava:18.0.
Could not find net.sf.kxml:kxml2:2.3.0.
Could not find org.ow2.asm:asm-analysis:5.0.4.
Could not find com.intellij:annotations:12.0.
Could not find com.google.jimfs:jimfs:1.1.
Could not find org.ow2.asm:asm:5.0.4.
Could not find org.ow2.asm:asm-commons:5.0.4.
Could not find net.sf.proguard:proguard-gradle:5.2.1.
Could not find org.jacoco:org.jacoco.core:0.7.5.201505241946.
Could not find org.jacoco:org.jacoco.report:0.7.5.201505241946.
Could not find net.sf.jopt-simple:jopt-simple:4.9.
Could not find com.google.protobuf:protobuf-java:2.5.0.
Could not find org.antlr:antlr:3.5.2.
Could not find com.squareup:javawriter:2.5.0.
Could not find org.bouncycastle:bcpkix-jdk15on:1.48.
Could not find org.bouncycastle:bcprov-jdk15on:1.48.
Could not find org.ow2.asm:asm-tree:5.0.4.
Could not find org.eclipse.jdt.core.compiler:ecj:4.5.1.
Could not find com.google.guava:guava:18.0.
Could not find org.antlr:antlr4:4.5.3.
Could not find commons-io:commons-io:2.4.
Could not find com.googlecode.juniversalchardet:juniversalchardet:1.0.3.
Could not find com.google.code.gson:gson:2.2.4.
Could not find org.apache.commons:commons-compress:1.8.1.
Could not find org.apache.httpcomponents:httpclient:4.1.1.
Could not find org.apache.httpcomponents:httpmime:4.1.
Could not find com.google.guava:guava:18.0.
Could not find net.sf.kxml:kxml2:2.3.0.
Could not find org.ow2.asm:asm-analysis:5.0.4.
Could not find com.intellij:annotations:12.0.
Could not find com.google.jimfs:jimfs:1.1.
pa...@gmail.com <pa...@gmail.com> #87
Yeah, I'm also working in a cordova project and still have the error... these are the ones I'm missing...
> Could not find gradle.jar (com.android.tools.build:gradle:2.2.3).
https://jcenter.bintray.com/com/android/tools/build/gradle/2.2.3/gradle-2.2.3.jar
> Could not find gradle-core.jar (com.android.tools.build:gradle-core:2.2.3).
https://jcenter.bintray.com/com/android/tools/build/gradle-core/2.2.3/gradle-core-2.2.3.jar
> Could not find builder.jar (com.android.tools.build:builder:2.2.3).
https://jcenter.bintray.com/com/android/tools/build/builder/2.2.3/builder-2.2.3.jar
> Could not find lint.jar (com.android.tools.lint:lint:25.2.3).
https://jcenter.bintray.com/com/android/tools/lint/lint/25.2.3/lint-25.2.3.jar
> Could not find gradle-api.jar (com.android.tools.build:gradle-api:2.2.3).
https://jcenter.bintray.com/com/android/tools/build/gradle-api/2.2.3/gradle-api-2.2.3.jar
> Could not find compilerCommon.jar (com.android.databinding:compilerCommon:2.2.3).
https://jcenter.bintray.com/com/android/databinding/compilerCommon/2.2.3/compilerCommon-2.2.3.jar
> Could not find builder-model.jar (com.android.tools.build:builder-model:2.2.3).
https://jcenter.bintray.com/com/android/tools/build/builder-model/2.2.3/builder-model-2.2.3.jar
> Could not find builder-test-api.jar (com.android.tools.build:builder-test-api:2.2.3).
https://jcenter.bintray.com/com/android/tools/build/builder-test-api/2.2.3/builder-test-api-2.2.3.jar
> Could not find sdklib.jar (com.android.tools:sdklib:25.2.3).
https://jcenter.bintray.com/com/android/tools/sdklib/25.2.3/sdklib-25.2.3.jar
> Could not find sdk-common.jar (com.android.tools:sdk-common:25.2.3).
https://jcenter.bintray.com/com/android/tools/sdk-common/25.2.3/sdk-common-25.2.3.jar
> Could not find common.jar (com.android.tools:common:25.2.3).
https://jcenter.bintray.com/com/android/tools/common/25.2.3/common-25.2.3.jar
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:25.2.3).
https://jcenter.bintray.com/com/android/tools/build/manifest-merger/25.2.3/manifest-merger-25.2.3.jar
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:25.2.3).
https://jcenter.bintray.com/com/android/tools/ddms/ddmlib/25.2.3/ddmlib-25.2.3.jar
> Could not find protos.jar (com.android.tools.analytics-library:protos:25.2.3).
https://jcenter.bintray.com/com/android/tools/analytics-library/protos/25.2.3/protos-25.2.3.jar
> Could not find shared.jar (com.android.tools.analytics-library:shared:25.2.3).
https://jcenter.bintray.com/com/android/tools/analytics-library/shared/25.2.3/shared-25.2.3.jar
> Could not find tracker.jar (com.android.tools.analytics-library:tracker:25.2.3).
https://jcenter.bintray.com/com/android/tools/analytics-library/tracker/25.2.3/tracker-25.2.3.jar
> Could not find lint-checks.jar (com.android.tools.lint:lint-checks:25.2.3).
https://jcenter.bintray.com/com/android/tools/lint/lint-checks/25.2.3/lint-checks-25.2.3.jar
> Could not find baseLibrary.jar (com.android.databinding:baseLibrary:2.2.3).
https://jcenter.bintray.com/com/android/databinding/baseLibrary/2.2.3/baseLibrary-2.2.3.jar
> Could not find layoutlib-api.jar (com.android.tools.layoutlib:layoutlib-api:25.2.3).
https://jcenter.bintray.com/com/android/tools/layoutlib/layoutlib-api/25.2.3/layoutlib-api-25.2.3.jar
> Could not find dvlib.jar (com.android.tools:dvlib:25.2.3).
https://jcenter.bintray.com/com/android/tools/dvlib/25.2.3/dvlib-25.2.3.jar
> Could not find repository.jar (com.android.tools:repository:25.2.3).
https://jcenter.bintray.com/com/android/tools/repository/25.2.3/repository-25.2.3.jar
> Could not find lint-api.jar (com.android.tools.lint:lint-api:25.2.3).
https://jcenter.bintray.com/com/android/tools/lint/lint-api/25.2.3/lint-api-25.2.3.jar
> Could not find annotations.jar (com.android.tools:annotations:25.2.3).
https://jcenter.bintray.com/com/android/tools/annotations/25.2.3/annotations-25.2.3.jar
> Could not find gradle.jar (com.android.tools.build:gradle:2.2.3).
> Could not find gradle-core.jar (com.android.tools.build:gradle-core:2.2.3).
> Could not find builder.jar (com.android.tools.build:builder:2.2.3).
> Could not find lint.jar (com.android.tools.lint:lint:25.2.3).
> Could not find gradle-api.jar (com.android.tools.build:gradle-api:2.2.3).
> Could not find compilerCommon.jar (com.android.databinding:compilerCommon:2.2.3).
> Could not find builder-model.jar (com.android.tools.build:builder-model:2.2.3).
> Could not find builder-test-api.jar (com.android.tools.build:builder-test-api:2.2.3).
> Could not find sdklib.jar (com.android.tools:sdklib:25.2.3).
> Could not find sdk-common.jar (com.android.tools:sdk-common:25.2.3).
> Could not find common.jar (com.android.tools:common:25.2.3).
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:25.2.3).
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:25.2.3).
> Could not find protos.jar (com.android.tools.analytics-library:protos:25.2.3).
> Could not find shared.jar (com.android.tools.analytics-library:shared:25.2.3).
> Could not find tracker.jar (com.android.tools.analytics-library:tracker:25.2.3).
> Could not find lint-checks.jar (com.android.tools.lint:lint-checks:25.2.3).
> Could not find baseLibrary.jar (com.android.databinding:baseLibrary:2.2.3).
> Could not find layoutlib-api.jar (com.android.tools.layoutlib:layoutlib-api:25.2.3).
> Could not find dvlib.jar (com.android.tools:dvlib:25.2.3).
> Could not find repository.jar (com.android.tools:repository:25.2.3).
> Could not find lint-api.jar (com.android.tools.lint:lint-api:25.2.3).
> Could not find annotations.jar (com.android.tools:annotations:25.2.3).
sa...@google.com <sa...@google.com> #88
The following plugins, which were previously available on JCenter, are now available on maven.google.com "
* com.google.firebase:firebase-plugins
* com.google.firebase:crash-plugin
* com.google.firebase:perf-plugin
You should be able to resolve issues with these by adding google() to your buildscript repositories block.
* com.google.firebase:firebase-plugins
* com.google.firebase:crash-plugin
* com.google.firebase:perf-plugin
You should be able to resolve issues with these by adding google() to your buildscript repositories block.
pa...@gmail.com <pa...@gmail.com> #89
When I do that I get:
> Could not find method google() for arguments [] on repository container.
> Could not find method google() for arguments [] on repository container.
sa...@google.com <sa...@google.com> #90
Note that if your build tools are older you may not be able to use google(), instead you can use maven { url 'https://maven.google.com ' } in its place. One is just a shorthand for the other.
See here for more information:
https://stackoverflow.com/questions/46467561/difference-between-google-and-maven-url-https-maven-google-com
See here for more information:
me...@gmail.com <me...@gmail.com> #92
For my Ionic/Cordova based project that depended on com.android.tools.build:gradle:2.2.3 in jCenter under the hood, I was able to gank this person's hook to update the repo urls: https://stackoverflow.com/a/36210134/3304034 .
I used the url suggested earlier in the thread (https://issuetracker.google.com/issues/120759347#comment85 - `maven { url 'https://dl.bintray.com/android/android-tools/ ' }`) and my builds are unstuck, just in time for my planned release today... Looking forward to removing the workaround :D
I used the url suggested earlier in the thread (
ca...@gmail.com <ca...@gmail.com> #93
Adding the following lines did not fix the issue for us.
maven {
url "https://google.bintray.com/flexbox-layout "
}
maven {
url "
}
mo...@gtempaccount.com <mo...@gtempaccount.com> #94
I was able to fix my issue for now by downgrading to com.android.tools.build:gradle:2.3.0, which has been on jcenter() all along...Waiting on 2.3.2 to be copied back to jcenter..
sp...@gmail.com <sp...@gmail.com> #95
maven { url 'https://dl.bintray.com/android/android-tools/ ' }
couldn't find grandle 3.0
A problem occurred configuring root project 'android'.
[16:46:45][Step 4/5] [ci:build:android-qa ] > Could not resolve all files for configuration ':classpath'.
[16:46:45][Step 4/5] [ci:build:android-qa ] > Could not find com.android.tools.build:gradle:3.0.0.
[16:46:45][Step 4/5] [ci:build:android-qa ] Searched in the following locations:
[16:46:45][Step 4/5] [ci:build:android-qa ]https://jcenter.bintray.com/com/android/tools/build/gradle/3.0.0/gradle-3.0.0.pom
[16:46:45][Step 4/5] [ci:build:android-qa ]https://jcenter.bintray.com/com/android/tools/build/gradle/3.0.0/gradle-3.0.0.jar
[16:46:45][Step 4/5] [ci:build:android-qa ]https://dl.bintray.com/android/android-tools/com/android/tools/build/gradle/3.0.0/gradle-3.0.0.pom
[16:46:45][Step 4/5] [ci:build:android-qa ]https://dl.bintray.com/android/android-tools/com/android/tools/build/gradle/3.0.0/gradle-3.0.0.jar
couldn't find grandle 3.0
A problem occurred configuring root project 'android'.
[16:46:45][Step 4/5] [ci:build:android-qa ] > Could not resolve all files for configuration ':classpath'.
[16:46:45][Step 4/5] [ci:build:android-qa ] > Could not find com.android.tools.build:gradle:3.0.0.
[16:46:45][Step 4/5] [ci:build:android-qa ] Searched in the following locations:
[16:46:45][Step 4/5] [ci:build:android-qa ]
[16:46:45][Step 4/5] [ci:build:android-qa ]
[16:46:45][Step 4/5] [ci:build:android-qa ]
[16:46:45][Step 4/5] [ci:build:android-qa ]
lo...@gmail.com <lo...@gmail.com> #96
this is costing me money
sa...@google.com <sa...@google.com> #97
JFrog has completed the restore so I am optimistic that this will issue should now be resolved. If you are still having trouble or think we missed re-adding any library to JCenter, please update us here. Thank you all for your patience!
ka...@gmail.com <ka...@gmail.com> #98
Thanks a lot.. it is working now.
dv...@gmail.com <dv...@gmail.com> #99
I am still seeing issues with com.android.tools.build:gradle:3.0.1
an...@gmail.com <an...@gmail.com> #100
i am able build com.android.tools.build:gradle:3.0.0
ka...@gmail.com <ka...@gmail.com> #101
manifest-merger-26.0.1.jar , ddmlib-26.0.1.jar , dvlib-26.0.1.jar , common-26.0.1.jar are still missing
ma...@gmail.com <ma...@gmail.com> #102
Still can't build
* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all files for configuration ':app:classpath'.
> Could not find gradle.jar (com.android.tools.build:gradle:2.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/2.3.1/gradle-2.3.1.jar
> Could not find gradle-core.jar (com.android.tools.build:gradle-core:2.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle-core/2.3.1/gradle-core-2.3.1.jar
> Could not find builder.jar (com.android.tools.build:builder:2.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/builder/2.3.1/builder-2.3.1.jar
> Could not find lint.jar (com.android.tools.lint:lint:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/lint/lint/25.3.1/lint-25.3.1.jar
> Could not find gradle-api.jar (com.android.tools.build:gradle-api:2.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle-api/2.3.1/gradle-api-2.3.1.jar
> Could not find compilerCommon.jar (com.android.databinding:compilerCommon:2.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/databinding/compilerCommon/2.3.1/compilerCommon-2.3.1.jar
> Could not find lint-checks.jar (com.android.tools.lint:lint-checks:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/lint/lint-checks/25.3.1/lint-checks-25.3.1.jar
> Could not find lint-api.jar (com.android.tools.lint:lint-api:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/lint/lint-api/25.3.1/lint-api-25.3.1.jar
> Could not find tracker.jar (com.android.tools.analytics-library:tracker:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/analytics-library/tracker/25.3.1/tracker-25.3.1.jar
> Could not find shared.jar (com.android.tools.analytics-library:shared:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/analytics-library/shared/25.3.1/shared-25.3.1.jar
> Could not find protos.jar (com.android.tools.analytics-library:protos:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/analytics-library/protos/25.3.1/protos-25.3.1.jar
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/manifest-merger/25.3.1/manifest-merger-25.3.1.jar
> Could not find sdk-common.jar (com.android.tools:sdk-common:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/sdk-common/25.3.1/sdk-common-25.3.1.jar
> Could not find builder-model.jar (com.android.tools.build:builder-model:2.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/builder-model/2.3.1/builder-model-2.3.1.jar
> Could not find builder-test-api.jar (com.android.tools.build:builder-test-api:2.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/builder-test-api/2.3.1/builder-test-api-2.3.1.jar
> Could not find sdklib.jar (com.android.tools:sdklib:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/sdklib/25.3.1/sdklib-25.3.1.jar
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/ddms/ddmlib/25.3.1/ddmlib-25.3.1.jar
> Could not find layoutlib-api.jar (com.android.tools.layoutlib:layoutlib-api:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/layoutlib/layoutlib-api/25.3.1/layoutlib-api-25.3.1.jar
> Could not find dvlib.jar (com.android.tools:dvlib:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/dvlib/25.3.1/dvlib-25.3.1.jar
> Could not find repository.jar (com.android.tools:repository:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/repository/25.3.1/repository-25.3.1.jar
> Could not find common.jar (com.android.tools:common:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/common/25.3.1/common-25.3.1.jar
> Could not find baseLibrary.jar (com.android.databinding:baseLibrary:2.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/databinding/baseLibrary/2.3.1/baseLibrary-2.3.1.jar
> Could not find annotations.jar (com.android.tools:annotations:25.3.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/annotations/25.3.1/annotations-25.3.1.jar
* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all files for configuration ':app:classpath'.
> Could not find gradle.jar (com.android.tools.build:gradle:2.3.1).
Searched in the following locations:
> Could not find gradle-core.jar (com.android.tools.build:gradle-core:2.3.1).
Searched in the following locations:
> Could not find builder.jar (com.android.tools.build:builder:2.3.1).
Searched in the following locations:
> Could not find lint.jar (com.android.tools.lint:lint:25.3.1).
Searched in the following locations:
> Could not find gradle-api.jar (com.android.tools.build:gradle-api:2.3.1).
Searched in the following locations:
> Could not find compilerCommon.jar (com.android.databinding:compilerCommon:2.3.1).
Searched in the following locations:
> Could not find lint-checks.jar (com.android.tools.lint:lint-checks:25.3.1).
Searched in the following locations:
> Could not find lint-api.jar (com.android.tools.lint:lint-api:25.3.1).
Searched in the following locations:
> Could not find tracker.jar (com.android.tools.analytics-library:tracker:25.3.1).
Searched in the following locations:
> Could not find shared.jar (com.android.tools.analytics-library:shared:25.3.1).
Searched in the following locations:
> Could not find protos.jar (com.android.tools.analytics-library:protos:25.3.1).
Searched in the following locations:
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:25.3.1).
Searched in the following locations:
> Could not find sdk-common.jar (com.android.tools:sdk-common:25.3.1).
Searched in the following locations:
> Could not find builder-model.jar (com.android.tools.build:builder-model:2.3.1).
Searched in the following locations:
> Could not find builder-test-api.jar (com.android.tools.build:builder-test-api:2.3.1).
Searched in the following locations:
> Could not find sdklib.jar (com.android.tools:sdklib:25.3.1).
Searched in the following locations:
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:25.3.1).
Searched in the following locations:
> Could not find layoutlib-api.jar (com.android.tools.layoutlib:layoutlib-api:25.3.1).
Searched in the following locations:
> Could not find dvlib.jar (com.android.tools:dvlib:25.3.1).
Searched in the following locations:
> Could not find repository.jar (com.android.tools:repository:25.3.1).
Searched in the following locations:
> Could not find common.jar (com.android.tools:common:25.3.1).
Searched in the following locations:
> Could not find baseLibrary.jar (com.android.databinding:baseLibrary:2.3.1).
Searched in the following locations:
> Could not find annotations.jar (com.android.tools:annotations:25.3.1).
Searched in the following locations:
tr...@google.com <tr...@google.com> #103
Re #101: Build tools v26.0.1 is hosted on maven.google.com , and has never been available via jCenter. This is working as intended. Only versions <26 were hosted on jCenter and were affected.
Re #102: All of those links are working for me when I click on them. Please try clearing your Gradle cache, because it should be finding those artifacts.
Re #102: All of those links are working for me when I click on them. Please try clearing your Gradle cache, because it should be finding those artifacts.
[Deleted User] <[Deleted User]> #104
Painful Problem for everyone we have fixed the issue using this workaround
buildscript {
repositories {
maven {
url "https://dl.bintray.com/android/android-tools "
}
}
}
When @google will fix the issue remove this workaround!!
buildscript {
repositories {
maven {
url "
}
}
}
When @google will fix the issue remove this workaround!!
jo...@gmail.com <jo...@gmail.com> #105
My builds started working! Thanks for the fix!
tr...@google.com <tr...@google.com> #106
At this point, it seems this issue is completely resolved. If you're still experiencing build issues, please open a new issue so we can triage individually.
Marking this as fixed. Additional followup is pending on mirroring old artifacts intomaven.google.com , and other tasks to strengthen artifact hosting (pending post-mortem).
Marking this as fixed. Additional followup is pending on mirroring old artifacts into
ka...@gmail.com <ka...@gmail.com> #107
The problem was resolved when I cleared my Gradle cache. So anybody having a problem should try that first.
pa...@gmail.com <pa...@gmail.com> #108
Hi, I'm working in a Ionic project and yesterday when I tried to build my app it couldn't find A LOT OF libraries... now there's ONLY ONE library that it couldn't find... please... help.
* What went wrong:
A problem occurred configuring root project 'android'.
> Could not find support-compat.aar (com.android.support:support-compat:26.1.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/support/support-compat/26.1.0/support-compat-26.1.0.aar
--- EDIT ---
Fixed it, if there's anyone who have the same problem I had this is what I did:
cordova plugin add cordova-android-support-gradle-release --variable ANDROID_SUPPORT_VERSION=25.+
* What went wrong:
A problem occurred configuring root project 'android'.
> Could not find support-compat.aar (com.android.support:support-compat:26.1.0).
Searched in the following locations:
--- EDIT ---
Fixed it, if there's anyone who have the same problem I had this is what I did:
cordova plugin add cordova-android-support-gradle-release --variable ANDROID_SUPPORT_VERSION=25.+
br...@gmail.com <br...@gmail.com> #109
Wildcards are generally frowned upon
mo...@gmail.com <mo...@gmail.com> #110
working on a react native project. few days ago it was working buh now experiencing this error.
> Could not resolve all files for configuration ':react-native-camera:classpath'.
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/manifest-merger/26.0.0/manifest-merger-26.0.0.jar
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:26.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/ddms/ddmlib/26.0.0/ddmlib-26.0.0.jar
> Could not find dvlib.jar (com.android.tools:dvlib:26.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/dvlib/26.0.0/dvlib-26.0.0.jar
> Could not find common.jar (com.android.tools:common:26.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/common/26.0.0/common-26.0.0.jar
> Could not resolve all files for configuration ':react-native-camera:classpath'.
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.0).
Searched in the following locations:
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:26.0.0).
Searched in the following locations:
> Could not find dvlib.jar (com.android.tools:dvlib:26.0.0).
Searched in the following locations:
> Could not find common.jar (com.android.tools:common:26.0.0).
Searched in the following locations:
fr...@gmail.com <fr...@gmail.com> #111
I imported and tried to build bluetoothlegatt example code and it looks that I have the same problem:
Build returns this error:
Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/manifest-merger/26.0.1/manifest-merger-26.0.1.jar
Is there any fix ?
Thanks
Franck
Version:
Android Studio 3.2.1
Build #AI-181.5540.7.32.5056338, built on October 9, 2018
JRE: 1.8.0_152-release-1136-b06 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
Build returns this error:
Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.1).
Searched in the following locations:
Is there any fix ?
Thanks
Franck
Version:
Android Studio 3.2.1
Build #AI-181.5540.7.32.5056338, built on October 9, 2018
JRE: 1.8.0_152-release-1136-b06 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
ay...@gmail.com <ay...@gmail.com> #112
Working on Unity project exported that project into android and experiencing this error
Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/manifest-merger/26.0.1/manifest-merger-26.0.1.jar
Even the projects that were working fine like 5 days ago they are also giving the same error. Please let me know if there's any work around or fix.
Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.1).
Searched in the following locations:
Even the projects that were working fine like 5 days ago they are also giving the same error. Please let me know if there's any work around or fix.
io...@gmail.com <io...@gmail.com> #113
Same here Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.0)
bo...@gmail.com <bo...@gmail.com> #114
Having exact same problem as #111 and #112
ERROR: Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.1).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/manifest-merger/26.0.1/manifest-merger-26.0.1.jar
ERROR: Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.1).
Searched in the following locations:
gl...@gmail.com <gl...@gmail.com> #115
#MeToo
do...@gmail.com <do...@gmail.com> #116
issue fixed
###
I have same issue, What do I have to do?
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':buildSrc:runtimeClasspath'.
at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.rethrowFailure(DefaultConfiguration.java:918)
at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.access$1600(DefaultConfiguration.java:116)
Cause 1: org.gradle.internal.resolve.ArtifactNotFoundException: Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.0).
Searched in the following locations:
http://jcenter.bintray.com/com/android/tools/build/manifest-merger/26.0.0/manifest-merger-26.0.0.jar
Cause 2: org.gradle.internal.resolve.ArtifactNotFoundException: Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:26.0.0).
Searched in the following locations:
http://jcenter.bintray.com/com/android/tools/ddms/ddmlib/26.0.0/ddmlib-26.0.0.jar
Cause 3: org.gradle.internal.resolve.ArtifactNotFoundException: Could not find dvlib.jar (com.android.tools:dvlib:26.0.0).
Searched in the following locations:
http://jcenter.bintray.com/com/android/tools/dvlib/26.0.0/dvlib-26.0.0.jar
Cause 4: org.gradle.internal.resolve.ArtifactNotFoundException: Could not find common.jar (com.android.tools:common:26.0.0).
Searched in the following locations:
http://jcenter.bintray.com/com/android/tools/common/26.0.0/common-26.0.0.jar
###
I have same issue, What do I have to do?
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':buildSrc:runtimeClasspath'.
at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.rethrowFailure(DefaultConfiguration.java:918)
at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.access$1600(DefaultConfiguration.java:116)
Cause 1: org.gradle.internal.resolve.ArtifactNotFoundException: Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.0).
Searched in the following locations:
Cause 2: org.gradle.internal.resolve.ArtifactNotFoundException: Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:26.0.0).
Searched in the following locations:
Cause 3: org.gradle.internal.resolve.ArtifactNotFoundException: Could not find dvlib.jar (com.android.tools:dvlib:26.0.0).
Searched in the following locations:
Cause 4: org.gradle.internal.resolve.ArtifactNotFoundException: Could not find common.jar (com.android.tools:common:26.0.0).
Searched in the following locations:
ha...@gmail.com <ha...@gmail.com> #117
I was also facing the same issue since 2 days ago. I followed some examples on net and just switched the order of maven and jcenter in build.gradle so that libraries are first downloaded from maven and then from jcenter if maven doesn't have them.
Here is what was working for me:
allprojects {
buildscript.repositories {
maven {
url "https://maven.google.com "
}
jcenter ({
url "http://jcenter.bintray.com "
})
}
repositories {
maven {
url "https://maven.google.com "
}
jcenter ({
url "http://jcenter.bintray.com "
})
}
}
Here is what was working for me:
allprojects {
buildscript.repositories {
maven {
url "
}
jcenter ({
url "
})
}
repositories {
maven {
url "
}
jcenter ({
url "
})
}
}
ad...@gmail.com <ad...@gmail.com> #118
Can anyone help with this issue. Something's wrong as earlier I was able to build successfully using the same code.
ERROR: Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.google.firebase:firebase-iid:[17.0.2].
Show Details
Affected Modules: app
ERROR: Unable to resolve dependency for ':app@debugAndroidTest/compileClasspath': Could not resolve com.google.firebase:firebase-iid:[17.0.2].
Show Details
Affected Modules: app
ERROR: Unable to resolve dependency for ':app@debugUnitTest/compileClasspath': Could not resolve com.google.firebase:firebase-iid:[17.0.2].
Show Details
Affected Modules: app
ERROR: Unable to resolve dependency for ':app@release/compileClasspath': Could not resolve com.google.firebase:firebase-iid:[17.0.2].
Show Details
Affected Modules: app
ERROR: Unable to resolve dependency for ':app@releaseUnitTest/compileClasspath': Could not resolve com.google.firebase:firebase-iid:[17.0.2].
Show Details
Affected Modules: app
ERROR: Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.google.firebase:firebase-iid:[17.0.2].
Show Details
Affected Modules: app
ERROR: Unable to resolve dependency for ':app@debugAndroidTest/compileClasspath': Could not resolve com.google.firebase:firebase-iid:[17.0.2].
Show Details
Affected Modules: app
ERROR: Unable to resolve dependency for ':app@debugUnitTest/compileClasspath': Could not resolve com.google.firebase:firebase-iid:[17.0.2].
Show Details
Affected Modules: app
ERROR: Unable to resolve dependency for ':app@release/compileClasspath': Could not resolve com.google.firebase:firebase-iid:[17.0.2].
Show Details
Affected Modules: app
ERROR: Unable to resolve dependency for ':app@releaseUnitTest/compileClasspath': Could not resolve com.google.firebase:firebase-iid:[17.0.2].
Show Details
Affected Modules: app
fe...@gmail.com <fe...@gmail.com> #119
Today I'm having the "ERROR: Could not find com.google.gms.google-services:4.2.0" issue on an old project I'm refactoring. I can't fix it by including either google() or any other solution previously posted. I'm using the last Android Studio version 3.3.2. What can I do??
Example:
buildscript {
repositories {
google()
jcenter()
maven {
url 'https://maven.fabric.io/public '
}
}
dependencies {
classpath 'com.android.tools.build:gradle:3.3.2'
classpath 'com.google.gms.google-services:4.2.0'
classpath 'io.fabric.tools:gradle:1.28.1'
}
}
allprojects {
repositories {
google()
jcenter()
}
}
EDIT:
Nevermind. the firebase crashlytics tutorial had this:
(found here:https://firebase.google.com/docs/crashlytics/get-started?authuser=0#android )
classpath 'com.google.gms.google-services:4.2.0'
Instead of:
classpath 'com.google.gms:google-services:4.2.0'
Example:
buildscript {
repositories {
google()
jcenter()
maven {
url '
}
}
dependencies {
classpath 'com.android.tools.build:gradle:3.3.2'
classpath 'com.google.gms.google-services:4.2.0'
classpath 'io.fabric.tools:gradle:1.28.1'
}
}
allprojects {
repositories {
google()
jcenter()
}
}
EDIT:
Nevermind. the firebase crashlytics tutorial had this:
(found here:
classpath 'com.google.gms.google-services:4.2.0'
Instead of:
classpath 'com.google.gms:google-services:4.2.0'
po...@gmail.com <po...@gmail.com> #120
Thanks a lot!
sa...@gmail.com <sa...@gmail.com> #121
Please anyone help me on the following issue, i have tried all the mentioned ratifications...
..
> cordova build android
cordova-android-support-gradle-release: Android platform: V7+
cordova-android-support-gradle-release: Wrote custom version '27.+' to E:\customer portal\My Nayatel\My Nayatel\platforms\android\app\build.gradle
cordova-android-support-gradle-release: Wrote custom version '27.+' to E:\customer portal\My Nayatel\My Nayatel\platforms\android\cordova-android-support-gradle-release\mynayatel-cordova-android-support-gradle-release.gradle
Android Studio project detected
cordova-android-support-gradle-release: Android platform: V7+
cordova-android-support-gradle-release: Wrote custom version '27.+' to E:\customer portal\My Nayatel\My Nayatel\platforms\android\app\build.gradle
cordova-android-support-gradle-release: Wrote custom version '27.+' to E:\customer portal\My Nayatel\My Nayatel\platforms\android\cordova-android-support-gradle-release\mynayatel-cordova-android-support-gradle-release.gradle
ANDROID_HOME=C:\Users\PC\AppData\Local\Android\sdk
JAVA_HOME=C:\Program Files\Java\jdk1.8.0_71
studio
Subproject Path: CordovaLib
Subproject Path: app
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring project ':CordovaLib'.
> Could not resolve all files for configuration ':CordovaLib:classpath'.
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/manifest-merger/26.0.0/manifest-merger-26.0.0.jar
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:26.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/ddms/ddmlib/26.0.0/ddmlib-26.0.0.jar
> Could not find dvlib.jar (com.android.tools:dvlib:26.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/dvlib/26.0.0/dvlib-26.0.0.jar
> Could not find common.jar (com.android.tools:common:26.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/common/26.0.0/common-26.0.0.jar
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
* Get more help athttps://help.gradle.org
BUILD FAILED in 4s
(node:8816) UnhandledPromiseRejectionWarning: Error: cmd: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring project ':CordovaLib'.
> Could not resolve all files for configuration ':CordovaLib:classpath'.
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/manifest-merger/26.0.0/manifest-merger-26.0.0.jar
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:26.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/ddms/ddmlib/26.0.0/ddmlib-26.0.0.jar
> Could not find dvlib.jar (com.android.tools:dvlib:26.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/dvlib/26.0.0/dvlib-26.0.0.jar
> Could not find common.jar (com.android.tools:common:26.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/common/26.0.0/common-26.0.0.jar
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
* Get more help athttps://help.gradle.org
BUILD FAILED in 4s
at ChildProcess.whenDone (E:\customer portal\My Nayatel\My Nayatel\platforms\android\cordova\node_modules\cordova-common\src\superspawn.js:169:23)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
(node:8816) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:8816) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
..
> cordova build android
cordova-android-support-gradle-release: Android platform: V7+
cordova-android-support-gradle-release: Wrote custom version '27.+' to E:\customer portal\My Nayatel\My Nayatel\platforms\android\app\build.gradle
cordova-android-support-gradle-release: Wrote custom version '27.+' to E:\customer portal\My Nayatel\My Nayatel\platforms\android\cordova-android-support-gradle-release\mynayatel-cordova-android-support-gradle-release.gradle
Android Studio project detected
cordova-android-support-gradle-release: Android platform: V7+
cordova-android-support-gradle-release: Wrote custom version '27.+' to E:\customer portal\My Nayatel\My Nayatel\platforms\android\app\build.gradle
cordova-android-support-gradle-release: Wrote custom version '27.+' to E:\customer portal\My Nayatel\My Nayatel\platforms\android\cordova-android-support-gradle-release\mynayatel-cordova-android-support-gradle-release.gradle
ANDROID_HOME=C:\Users\PC\AppData\Local\Android\sdk
JAVA_HOME=C:\Program Files\Java\jdk1.8.0_71
studio
Subproject Path: CordovaLib
Subproject Path: app
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring project ':CordovaLib'.
> Could not resolve all files for configuration ':CordovaLib:classpath'.
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.0).
Searched in the following locations:
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:26.0.0).
Searched in the following locations:
> Could not find dvlib.jar (com.android.tools:dvlib:26.0.0).
Searched in the following locations:
> Could not find common.jar (com.android.tools:common:26.0.0).
Searched in the following locations:
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
* Get more help at
BUILD FAILED in 4s
(node:8816) UnhandledPromiseRejectionWarning: Error: cmd: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring project ':CordovaLib'.
> Could not resolve all files for configuration ':CordovaLib:classpath'.
> Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.0).
Searched in the following locations:
> Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:26.0.0).
Searched in the following locations:
> Could not find dvlib.jar (com.android.tools:dvlib:26.0.0).
Searched in the following locations:
> Could not find common.jar (com.android.tools:common:26.0.0).
Searched in the following locations:
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
* Get more help at
BUILD FAILED in 4s
at ChildProcess.whenDone (E:\customer portal\My Nayatel\My Nayatel\platforms\android\cordova\node_modules\cordova-common\src\superspawn.js:169:23)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
(node:8816) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:8816) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
as...@gmail.com <as...@gmail.com> #122
ti...@brbcard.com.br <ti...@brbcard.com.br> #123
I deleted the line "cordova.gradle.include.5 = cordova-support-google-services / letterobrbapp-build.gradle" inside platforms/android/project.properties and the build worked.
da...@gmail.com <da...@gmail.com> #124
tried almost everything online but unfortunately been unable to build. keep getting this error
Error:Could not find com.android.tools.build:gradle:3.0.0.
Searched in the following locations:
- file:/C:/Program Files/Android/Android Studio/gradle/m2repository/com/android/tools/build/gradle/3.0.0/gradle-3.0.0.pom
-https://jcenter.bintray.com/com/android/tools/build/gradle/3.0.0/gradle-3.0.0.pom
Required by:
project :
Error:Could not find com.android.tools.build:gradle:3.0.0.
Searched in the following locations:
- file:/C:/Program Files/Android/Android Studio/gradle/m2repository/com/android/tools/build/gradle/3.0.0/gradle-3.0.0.pom
-
Required by:
project :
br...@gmail.com <br...@gmail.com> #125
Have you tried updating your dependencies? The build tools dont have to specified directly anymore with later versions of the android gradle plugin. (AGP)
da...@gmail.com <da...@gmail.com> #126
Comment has been deleted.
da...@gmail.com <da...@gmail.com> #127
thanks...solved
lu...@gmail.com <lu...@gmail.com> #128
#Me too!
og...@gmail.com <og...@gmail.com> #129
I have same problem , could you give me the solution that you have achieved?
pa...@gmail.com <pa...@gmail.com> #130
I am currently experiencing this at the moment. Is there a permanent solution for this?
ep...@gmail.com <ep...@gmail.com> #131
yi...@gmail.com <yi...@gmail.com> #132
Hello! I am currently experiencing the issue described in this thread too. How do you:
"the permanent solution is to switch to artifacts that can be found in other repositories."?
Thank you!
"the permanent solution is to switch to artifacts that can be found in other repositories."?
Thank you!
Description
AS returns :
Could not find com.google.gms:google-services:4.2.0.
Searched in the following locations:
-
-
-
-
-
-
-
-
Required by:
project :
Here my top project gradle build file :
buildscript {
repositories {
google()
jcenter()
maven {
url '
}
}
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.10"
classpath 'com.google.gms:google-services:4.2.0'
classpath 'io.fabric.tools:gradle:1.26.1'
}
}
allprojects {
repositories {
google()
jcenter()
maven { url '
maven { url '
maven { url "
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}