Obsolete
Status Update
No update yet.
Comments
vi...@google.com
il...@gmail.com
vi...@google.com
looks like google() is not working as expected and you have to manually add a maven entry for every library you need
lf...@google.com
le...@google.com
le...@google.com
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:
-
-
-
-
il...@gmail.com
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
le...@google.com
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 -
il...@gmail.com
google-servies:4.2.0 is back but firebase-plugins:1.1.5 is still missing.
ck...@gmail.com
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:
lu...@gmail.com
Also com.google.android:flexbox:0.2.6 (and com.google.android:flexbox:1.0.0)
sk...@googlemail.com
I think the larger developer community would appreciate an estimate or status report here.
km...@gmail.com
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.
[Deleted User] <[Deleted User]>
Or at least have some QA tests in place for such changes?
ga...@gtempaccount.com
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:
mt...@gmail.com
Any updates on firebase-plugins:1.1.5 ? I'm still not able to build
ba...@dytter.com
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
iw...@gmail.com
`com.google.android.exoplayer:exoplayer:2.X.X` doesn't work as well.
da...@mail.dk
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...
pu...@gmail.com
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.
ga...@gmail.com
What a silly decision on Google's part. Hopefully this is resolved soon.
si...@old.busybusy.com
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.
zb...@gmail.com
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
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 '
mi...@mikehardy.net
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()?
bo...@google.com
mi...@mikehardy.net
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.
pi...@gmail.com
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
mi...@mikehardy.net
@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!
pr...@gmail.com
Is it possible to roll back the changes? I have a few developers that can't build the project! Any workaround?
ru...@gmail.com
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
ju...@gmail.com
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/
Description
Android Studio Version: 3.5.0-2
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 29.3.4-6110076
HAXM / KVM Version: KVM 12.0.0
Android SDK Tools: 26.1.1
Host Operating System: Linux Mint 19.2 Tina
CPU Manufacturer: Intel CPU
Virtualization is supported
64-bit CPU
RAM: 15943 MB
GPU:
Build Fingerprint: Android/sdk_google_cheets_x86/cheets_x86:7.1.1/NMF19/4890193:userdebug/dev-keys
AVD Details: Name: Pixelbook_beta_API_25
CPU/ABI: x86
Path: /home/nfs/ili/.android/avd/Pixelbook_beta_API_25.avd
Target: chromeos [Chrome OS 67] (API level 25)
Skin: 1200x800
SD Card: 512M
AvdId: Pixelbook_beta_API_25
PlayStore.enabled: false
avd.ini.displayname: Pixelbook (beta) API 25
avd.ini.encoding: UTF-8
disk.dataPartition.size: 800M
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: no
fastboot.forceFastBoot: yes
hw.accelerometer: no
hw.arc: true
hw.audioInput: yes
hw.battery: yes
hw.camera.back: virtualscene
hw.camera.front: emulated
hw.cpu.ncore: 4
hw.dPad: no
hw.device.hash2: MD5:405787b829ba3c5f5644ae879d8aa175
hw.device.manufacturer: Google
hw.gps: no
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: landscape
hw.keyboard: yes
hw.keyboard.lid: yes
hw.lcd.density: 240
hw.lcd.height: 800
hw.lcd.width: 1200
hw.mainKeys: no
hw.ramSize: 2048
hw.sdCard: yes
hw.sensors.orientation: no
hw.sensors.proximity: no
hw.trackBall: no
image.sysdir.1: system-images/chromeos-67/chromeos/x86/
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: no
skin.dynamic: yes
skin.path.backup: _no_skin
tag.display: Chrome OS 67
vm.heapSize: 48
Steps to Reproduce Bug:1. Created a chrome os emulator following the guide here:
2. Start the emulator
Expected Result: Emulator is shown
Actual Result: Black Screen shown. Unable to use the emulator
Expected Behavior:
Observed Behavior: