IssueTracker

Hello, I would also add exoplayer 2.X and firebase-plugins 1.1.5.
I had to add this temporarily to my gradle file:

        maven { url 'https://google.bintray.com/exoplayer/' }
        maven { url 'https://dl.bintray.com/android/android-tools' }
        maven { url 'https://dl.bintray.com/firebase/gradle/' }

looks like google() is not working as expected and you have to manually add a maven entry for every library you need

`google-services` disapears from `com.google.android.gms` at https://dl.google.com/dl/android/maven2/index.html

Temporary workaround
You can grab google-services at https://dl.bintray.com/android/android-tools/com/google/gms/google-services/

Add this on your build script repositories :
        maven { url 'https://dl.bintray.com/android/android-tools' }

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

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

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

google-servies:4.2.0 is back but firebase-plugins:1.1.5 is still missing.

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:

Also com.google.android:flexbox:0.2.6 (and com.google.android:flexbox:1.0.0)

I think the larger developer community would appreciate an estimate or status report here.

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.

Or at least have some QA tests in place for such changes?

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:

Any updates on firebase-plugins:1.1.5 ? I'm still not able to build

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

`com.google.android.exoplayer:exoplayer:2.X.X` doesn't work as well.

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...

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.

What a silly decision on Google's part. Hopefully this is resolved soon.

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.

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/' }"

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()?

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.

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

@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!

Is it possible to roll back the changes? I have a few developers that can't build the project! Any workaround?

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 on maven.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

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/

Hi Sam,

Do you have any updates regarding the other libraries?

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

Yeah, It looks like `com.android.tools.build:gradle:2.3.3` is hosted nowhere at the moment

We're still working with jCenter to restore the remaining missing packages. We'll continue to provide updates here as they become available.

### 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 on bintray.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 both jcenter.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 from bintray.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 from bintray.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 from https://bintray.com/google.

   For bintray.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 into maven.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 from maven.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.