Android Studio修改版本号后Gradle同步报错‘Failed to resolve’求助

Hey there, fellow Android Studio newbie! I’ve been exactly where you are—frustrated after updating Gradle like the IDE asked, only to hit those annoying "Failed to resolve" errors. Let’s break down the fixes that actually worked for me and other devs facing this same problem:

Common Fixes to Try #

1. Double-Check Your Repository Configurations #

Gradle needs clear directions on where to pull dependencies from, and updating Gradle often means adjusting your repo setup.

• Open your project's settings.gradle (or settings.gradle.kts for Kotlin DSL) and make sure you have these repositories listed in this order in the dependencyResolutionManagement block:

  repositories {
      google()
      mavenCentral()
      // Only add other trusted repos here if you explicitly need them
  }
  

• For older project structures, also verify your project-level build.gradle (or build.gradle.kts) has the same repos in both the buildscript and allprojects blocks.

2. Clear Corrupted Gradle Caches #

Corrupted caches are one of the most frequent causes of this issue. Let’s wipe them clean:

• Go to File > Invalidate Caches... in Android Studio, check Invalidate and Restart, and let the IDE restart completely.
• If that doesn’t do the trick, manually delete the .gradle folder in your project’s root directory, plus the ~/.gradle/caches folder in your user home directory (on Windows, this is C:\Users\[YourName]\.gradle\caches).

3. Verify Dependency Versions and Compatibility #

Updating Gradle can break compatibility with older dependency versions.

• For every "Failed to resolve" entry, double-check that the version number is correct (no typos!) and that it’s supported with your new Gradle/Android Gradle Plugin (AGP) version.
• Avoid using wildcard versions like implementation 'com.example:library:+'—they’re unstable and often lead to resolution failures. Stick to explicit, stable version numbers.

4. Match AGP and Gradle Versions #

This is critical! AGP and Gradle have strict compatibility rules—updating one without the other will almost certainly cause errors.

• Here are some common compatible pairs to reference:
  • AGP 7.4.x ↔ Gradle 7.5
  • AGP 8.0.x ↔ Gradle 8.0+
• Confirm your AGP version (in the project-level build.gradle) matches the Gradle version specified in gradle/wrapper/gradle-wrapper.properties (look for the distributionUrl line).

5. Disable Offline Mode and Check Proxy Settings #

• If Gradle is set to offline mode, it can’t download new dependencies. Go to File > Settings > Build, Execution, Deployment > Build Tools > Gradle and uncheck Offline work.
• If you’re using a proxy, ensure it’s configured correctly in File > Settings > Appearance & Behavior > System Settings > HTTP Proxy. Try disabling the proxy temporarily to rule out connection issues.

6. Test with a Fresh Project #

If all else fails, create a new empty Android project and try syncing it. If the new project syncs successfully, compare its settings.gradle, build.gradle, and gradle-wrapper.properties files with your problematic project—you’ll likely spot a misconfiguration in the old project that’s causing the resolution errors.

内容的提问来源于stack exchange，提问作者Twitchy