Edit

Gradle build after JCenter shutdown

  • Article

Important

Visual Studio App Center is scheduled for retirement on March 31, 2025. While you can continue to use Visual Studio App Center until it is fully retired, there are several recommended alternatives that you may consider migrating to.

Learn more about support timelines and alternatives.

If you use JCenter and Bintray resources in your AppCenter Android builds and your builds fail on Gradle Task failure (could not get resource error), it's because JCenter Bintray is being shut down. Following lines (from Build Logs) illustrate this problem:

Resolved com.android.tools.build:gradle:3.5.4 in :classpath 
Resolved com.google.gms:google-services:4.2.0 in :classpath 
Project mobileapp at : is either no Android app project or build version has not been set to override. Skipping...
Configure project :@react-native-community_async-storage
Project @react-native-community_async-storage at :@react-native-community_async-storage is either no Android app project or build version has not been set to override.
* What went wrong:
Execution failed for task ':app:***'.
Could not resolve all files for configuration ':app:lintClassPath'.
Could not download groovy-all.jar (org.codehaus.groovy:groovy-all:2.4.15)
Could not get resource 'https://jcenter.bintray.com/org/codehaus/groovy/groovy-all/2.4.15/groovy-all-2.4.15.jar'.
Could not GET 'https://jcenter.bintray.com/org/codehaus/groovy/groovy-all/2.4.15/groovy-all-2.4.15.jar'.

This problem is caused by the fact that JFrog has shutdown JCenter (part of Bintray) on May 1, 2021. The JCenter was important part of Android development because a major fraction of Android artifacts were hosted on this site. Android developers should port their libraries to Maven Central with precaution that some old libraries are no longer maintained. These posts tell you what you need to know and do to avoid disruptions to your build pipelines.