Android Cloud Build failures - jcenter files can't be found

Cloud Builds on our project have been failing since this morning for us, trying to build to latest 2018.1 for Android. Failing on the same issue every time. I tried doing a clean build but still got the same errors.

Gradle builds are failing whilst trying to resolve files from the locations specified:
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

You can see by checking against these links that wherever they're coming from are reporting 404 errors for those files, they don't seem to exist any more.

I followed the paths from the base URL there and when I started writing this comment, when you reached this point, the only folder that existed was 0.5.3:

http://jcenter.bintray.com/com/android/tools/build/gradle/

Now, I can no longer find the 'tools' folder inside '/com/android/'. Like jcenter is currently unpublishing/removing a bunch of modules? Does Unity rely on these to be available?

This is the section of the log displaying the error:

 

I've been keeping an eye on Twitter and this solution worked for me for now, worth keeping an eye on for Android builds though:

https://twitter.com/ReleasesHub/status/1072175946747256832

I also found out from another Twitter user that this is an issue currently being monitored in Google's GitHub issues: https://github.com/google/ExoPlayer/issues/5225

 

the solution above is not working for us, anyone having this issue too?

 

https://issuetracker.google.com/issues/120759347#comment27

So Bintray, who provide the binaries through jcenter, are saying Google asked them to pull the binaries down.

Google are now saying this was not the intention and they intend to put them back.

I'm frankly surprised that this issue hasn't hit more Unity developers or if it has, why nobody seems to be talking about it. I've reached out in a couple of places and barring some native Android developers who are also feeling this, I haven't seen anything. My surprise comes from the fact that (at least for 2018.1.4f1, the version we're using) the default mainTemplate.gradle file from Unity uses jcenter to provide binaries for gradle builds, and I'd imagine there are a few Unity Android devs who don't deviate from that default file.

 

This work-around has now failed on us. Is there anyone at Unity who can provide an update on this? Are Unity aware of the situation and how it's affecting Android builds in Cloud Build?

 

hey, I was able to compile after migrating to unity 2018.2.16f1 using gradle 3.0.1 and the google() repository