title: Replacing jcenter() in Android Gradle Repositories
body: <p>Per <a href="https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/" rel="noreferrer">JFrog</a>, they are sunsetting Bintray (which includes JCenter) on May 1st, 2021.</p>
  <p>To prep for this, I opened my <code>build.gradle</code> and replaced <code>jcenter()</code> with <code>mavenCentral()</code>. My <code>build.gradle</code> now looks like this (with some parts removed):</p>
  <pre><code>buildscript {
      repositories {
          google()
          // jcenter()
          mavenCentral()
      }
  
      dependencies {
          // ...
      }
  }
  
  allprojects {
      repositories {
          google()
          // jcenter()
          mavenCentral()
  
          maven {
              url &quot;https://jitpack.io&quot;
          }
      }
  }
  
  </code></pre>
  <p>However, since replacing <code>jcenter()</code> with <code>mavenCentral()</code>, I receive this error:</p>
  <pre><code>A problem occurred configuring root project 'Redacted'.
  &gt; Could not resolve all artifacts for configuration ':classpath'.
     &gt; Could not find org.jetbrains.trove4j:trove4j:20160824.
       Searched in the following locations:
         - https://dl.google.com/dl/android/maven2/org/jetbrains/trove4j/trove4j/20160824/trove4j-20160824.pom
         - https://repo.maven.apache.org/maven2/org/jetbrains/trove4j/trove4j/20160824/trove4j-20160824.pom
       Required by:
           project : &gt; com.android.tools.build:gradle:4.1.2 &gt; com.android.tools.build:builder:4.1.2 &gt; com.android.tools:sdk-common:27.1.2
  
  Possible solution:
   - Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html
  </code></pre>
  <p>Is there another repository I can add to resolve this, or does <code>com.android.tools:sdk-common</code> need to update to use a different version of <code>org.jetbrains.trove4j:trove4j</code>?</p>
  <p><strong>Update:</strong> Version 4.1.3 still has the same issue.</p>