# Gradle: “Could not resolve all files for configuration”

> Gradle: Could not resolve all files for configuration. Add the missing repository, replace JCenter, fix the version, or check offline and proxy settings.

Canonical: https://app369.com/fix/android-gradle-could-not-resolve-all-files/
Last updated: 2026-11-07

An Android, Flutter or React Native build stops with Could not resolve all files for configuration ':app:debugRuntimeClasspath', followed by Could not find (or Could not resolve) and a library name. Gradle looked in the listed repositories and could not download that library at that version. The lines under the error name the exact artifact and the places Gradle searched.

**Short answer**

Read the “Could not find” line and the “Searched in the following locations” list under it. If the library is not on google() or mavenCentral(), add the repository it is published to in settings.gradle. If the list includes jcenter(), replace it, because JCenter is read-only. If the version does not exist, fix the typo or pick a published version. If nothing downloads at all, turn off Gradle offline mode, check the proxy settings, and run ./gradlew --refresh-dependencies.

## **Why Gradle can’t download it, and the fix**

1. 01 ### **The repository is not declared**
  > “Gradle looks for the files in whichever online repositories are specified in the dependencyResolutionManagement { repositories {...} } block of your settings.gradle file.” [**Android Developers, Manage remote repositories**](https://developer.android.com/build/remote-repositories) Gradle only searches the repositories you list. Newer projects list them in settings.gradle (dependencyResolutionManagement); Flutter and React Native projects often still list them in android/build.gradle under allprojects { repositories { ... } }. Libraries published to JitPack or a vendor’s own Maven repository need that repository added in whichever place your project uses.```
// settings.gradle.kts
dependencyResolutionManagement {
  repositories {
    google()
    mavenCentral()
    maven { url = uri("https://jitpack.io") }
  }
}

// Groovy (build.gradle): maven { url "https://jitpack.io" }
```
2. 02 ### **An old project still relies on JCenter**
  > “The JCenter repository, which was included by default in the past, became read-only on March 31st, 2021.” [**Android Developers, Manage remote repositories**](https://developer.android.com/build/remote-repositories) Older projects and plugins list jcenter(), and some old library versions only exist there. Replace jcenter() with mavenCentral() and update libraries to versions published on Maven Central.
3. 03 ### **Project repositories are blocked** With repositoriesMode set to FAIL_ON_PROJECT_REPOS, repositories declared in a module’s build.gradle are ignored or rejected. Move them into dependencyResolutionManagement in settings.gradle so every module uses them.
4. 04 ### **The Android Gradle plugin itself can’t be found (:classpath)**
  > “The order in which you list each repository determines the order in which Gradle searches the repositories for each project dependency.” [**Android Developers, Manage remote repositories**](https://developer.android.com/build/remote-repositories) Could not resolve all files for configuration ':classpath' or Could not find com.android.tools.build:gradle is about build plugins, not app libraries. Plugins come from the pluginManagement repositories in settings.gradle (or buildscript { repositories } in older projects), so add google(), mavenCentral() and gradlePluginPortal() there, and check the plugin version exists.```
// settings.gradle.kts
pluginManagement {
  repositories {
    google()
    mavenCentral()
    gradlePluginPortal()
  }
}
```
5. 05 ### **Flutter: io.flutter:flutter_embedding not found** The Flutter engine artifacts come from Flutter’s own Maven repository, which the Flutter Gradle plugin normally adds. A custom repositories block with FAIL_ON_PROJECT_REPOS, or an old plugin setup, can leave it out. Run flutter clean and flutter pub get, update to the current Flutter Gradle plugin setup, or add https://storage.googleapis.com/download.flutter.io as a Maven repository.
6. 06 ### **Offline mode, a proxy or a version that does not exist** Gradle offline mode in Android Studio, a corporate proxy or a firewall stops every download. A typo in the version, or a version that was never published, fails only for that library. Check the version on the repository’s website, then refresh.```
./gradlew build --refresh-dependencies
```

Checked against the vendor’s docs on November 7, 2026: [Android Developers: Manage remote repositories](https://developer.android.com/build/remote-repositories); [Android Developers: Fix dependency resolution errors](https://developer.android.com/build/dependency-resolution-errors).

## **Rather hand it over?**

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

- [from $450**App Fix Ticket**One reproducible bug in an existing mobile or web app, diagnosed and fixed.**See scope and start**](https://app369.com/fixed-price/flutter-firebase-bug-fix/)
- [from $450**AI-Built App Rescue**A Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.****No issues worth fixing, no charge.**** If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.**See scope and start**](https://app369.com/fixed-price/ai-app-rescue/)

Related: [**Android “Duplicate class found in modules”**](https://app369.com/fix/android-duplicate-class/) · [**Flutter “Gradle task assembleDebug failed”**](https://app369.com/fix/flutter-gradle-assembledebug-failed/) · [**Expo EAS build failed**](https://app369.com/fix/expo-eas-build-failed/)

Questions

## **More on this error**

<details>

<summary>**It worked yesterday and nothing changed. Why? **+</summary>

A dynamic version (1.+ or latest.release) moved to a release that is not available, a repository was down, or a cached file was removed. Pin exact versions, and run the build again with --refresh-dependencies.

</details>

<details>

<summary>**Why does it fail on CI but not on my machine? **+</summary>

Your machine has the library in its Gradle cache. The CI machine downloads from scratch and hits the missing repository or version. Fix the repository list so a clean build works.

</details>

<details>

<summary>**Can you fix it for me? **+</summary>

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

</details>

A different error?

## **Describe it and get a written quote**

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.

[**Describe your problem **→](https://app369.com/contact/) [**All fixes**](https://app369.com/fix/)