Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.android.support:appcompat-v7:26.1.0

Question

Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.android.support:appcompat-v7:26.1.0.

Could not resolve com.android.support:appcompat-v7:26.1.0.

Required by: project :app

No cached version of com.android.support:appcompat-v7:26.1.0 available for offline mode.

Error log:

Could not resolve all files for configuration ':app:debugCompileClasspath'.
Could not resolve com.android.support:appcompat-v7:26.1.0.
Required by:
project :app
No cached version of com.android.support:appcompat-v7:26.1.0 available for offline mode.
No cached version of com.android.support:appcompat-v7:26.1.0 available for offline mode.
Could not resolve com.android.support.constraint:constraint-layout:1.1.0-beta3.
Required by:
project :app
No cached version of com.android.support.constraint:constraint-layout:1.1.0-beta3 available for offline mode.
No cached version of com.android.support.constraint:constraint-layout:1.1.0-beta3 available for offline mode.
Could not resolve com.android.support:design:26.1.0.
Required by:
project :app
No cached version of com.android.support:design:26.1.0 available for offline mode.
No cached version of com.android.support:design:26.1.0 available for offline mode.
Could not resolve com.android.support:cardview-v7:26.1.0.
Required by:
project :app
No cached version of com.android.support:cardview-v7:26.1.0 available for offline mode.
No cached version of com.android.support:cardview-v7:26.1.0 available for offline mode.
Could not resolve com.google.android.gms:play-services-ads:11.4.2.
Required by:
project :app
No cached version of com.google.android.gms:play-services-ads:11.4.2 available for offline mode.
No cached version of com.google.android.gms:play-services-ads:11.4.2 available for offline mode.
Could not resolve com.android.support:support-v4:26.1.0.
Required by:
project :app
No cached version of com.android.support:support-v4:26.1.0 available for offline mode.
No cached version of com.android.support:support-v4:26.1.0 available for offline mode.

Error log image:

Click here for image

If you are using a VPN turn it off to get it to work. – Treewallie Oct 07 '19 at 17:05 — Treewallie, Oct 07 '19 at 17:05

score 140 · Accepted Answer · edited Mar 29 '18 at 21:20

140

Go to File->Other Settings->Default Settings->Build, Execution, Deployment->Build Tools->Gradle->Uncheck Offline work option.

edited Mar 29 '18 at 21:20

Scott Smith

3,900
2
31
63

answered Nov 04 '17 at 18:45

Mateus Preste

1,558
1
12
6

2

You should invalidate your cache and restart. Follow this steps `file` -> `invalidate caches/Restart` Then select `invalidate and restart` in the dialog box that appears. – Olaoye Oluwapelumi Apr 07 '19 at 07:49
You need to sync the project again. – Syyam Noor Jun 11 '19 at 18:35
2

I don't find this option available in the Android studo – Arefe Aug 15 '19 at 12:27
1

@Arefe It has since moved to the dedicated Gradle panel on the right side of the main window where a dedicated "Toggle Offline Mode" button can be clicked. – Edric Nov 12 '19 at 08:30
8

for me this option is uncheck but i have this error – Nov 30 '19 at 08:19

score 36 · Answer 2 · 2018-03-15T08:41:25.517

Below is a workaround demo image of ; Uncheck Offline work option by going to:

File -> Settings -> Build, Execution, Deployment -> Gradle

If above workaround not works then try this:

Open the build.gradle file for your application.
Make sure that the repositories section includes a maven section with the "https://maven.google.com" endpoint. For example:
allprojects {
     repositories {
         jcenter()
         maven {
             url "https://maven.google.com"
         }
     }
}
Add the support library to the dependencies section. For example, to add the v4 core-utils library, add the following lines:
dependencies {
    ...
    compile "com.android.support:support-core-utils:27.1.0"
}
Caution: Using dynamic dependencies (for example, palette-v7:23.0.+) can cause unexpected version updates and regression incompatibilities. We recommend that you explicitly specify a library version (for example, palette-v7:27.1.0).

Manifest Declaration Changes

Specifically, you should update the android:minSdkVersion element of the <uses-sdk> tag in the manifest to the new, lower version number, as shown below:
<uses-sdk
  android:minSdkVersion="14"
  android:targetSdkVersion="23" />
If you are using Gradle build files, the minSdkVersion setting in the build file overrides the manifest settings.
apply plugin: 'com.android.application'

android {
   ...
      defaultConfig {
            minSdkVersion 16
            ...
        }
        ...
    }

Following Android Developer Library Support.

score 16 · Answer 3 · edited Mar 28 '18 at 07:20

16

Just went to build.gradle and deleted the line:

implementation 'com.android.support:appcompat-v7:26.1.0'

After that, I re-synced the Gradle. Then, I pasted the line of code back, re-synced the Gradle again and it worked.

Note: While I was making this changes, I also updated all the SDK Tools that needed update.

edited Mar 28 '18 at 07:20

answered Nov 10 '17 at 23:27

benjamin

169
2

score 8 · Answer 4 · edited Jun 20 '20 at 09:12

8

`Invalidate Cache / Restart` from File option.

Just unchecking offline mode did not work for me.

edited Jun 20 '20 at 09:12

Community

1
1

answered Aug 20 '18 at 05:23

Khemraj Sharma

57,232
27
203
212

The option seems unavailable now in the Android studio – Arefe Aug 15 '19 at 12:28

score 7 · Answer 5 · answered Jan 01 '20 at 16:58

7

In the android\app\build.gradle file,

Replace the version details

implementation 'com.android.support:appcompat-v7:26.1.0'

with

implementation 'com.android.support:appcompat-v7:+'

Android Studio will use a suitable version to make it work for you.

answered Jan 01 '20 at 16:58

Collins USHI

567
7
17

score 6 · Answer 6 · answered Jun 01 '18 at 12:10

6

use Invalidate Caches/Restart it will works for you and make sure that your gradle offline sync option is not enabled

answered Jun 01 '18 at 12:10

Koorosh Ghorbani

507
4
14

score 6 · Answer 7 · answered Jun 11 '18 at 11:55

6

Adding this in project gradle worked for me

allprojects {
 repositories {
     jcenter()
     maven {
         url "https://maven.google.com" // specifically this worked 
     }
 }}

answered Jun 11 '18 at 11:55

zohaib khaliq

697
10
17

score 4 · Answer 8 · answered Oct 26 '19 at 14:47

4

This is a problem for users who live in a country that is banned by Google (like Iran). for this reason we need to remove these restrictions by a proxy. follow me :

file->settings->Appearance&Behavior->System Setting-> Http Proxy-> Manual proxy configuration ->HTTP -> Host name : fodev.org ->Port : 8118 .

and click Ok Button. then go to file-> Invalidate Caches/Restart . . . Use and enjoy the correct execution without error ;)

answered Oct 26 '19 at 14:47

Ali Yazdanifar

372
4
12

in iran we use shecan dot iran service ;) do you? i changed my dns and its worked – saber tabatabaee yazdi Nov 17 '19 at 16:29
1

shekan just can open the developers.android and cant open other websites like medician.com and interanet websites – Ali Yazdanifar Jun 13 '20 at 20:19

score 1 · Answer 9 · answered Sep 04 '18 at 08:21

Today I have the similar problem.

Previous in my project gradle

// Top-level build file where you can add configuration options common to all 
sub-projects/modules.
allprojects {
repositories {
    jcenter()
    google()
    mavenCentral()
    maven { url "https://jitpack.io" }
    maven { url 'https://plugins.gradle.org/m2/'}
}}

Then I just added this below line in allprojects

maven {
        url "https://maven.google.com"
    }

It saved my day.

And now my current allproject {} code looks like this

allprojects {
repositories {
    jcenter()
    google()
    mavenCentral()
    maven { url "https://jitpack.io" }
    maven { url 'https://plugins.gradle.org/m2/'}
    maven {
        url "https://maven.google.com"
    }
}}

score 1 · Answer 10 · answered Dec 19 '18 at 07:03

1

From the documentations:

Add the support library to the dependencies section. For example, to add the v4 core-utils library, add the following lines:
dependencies {
    ...
    implementation "com.android.support:support-core-utils:28.0.0"
}

answered Dec 19 '18 at 07:03

Ghasem

14,455
21
138
171

score 1 · Answer 11 · answered Jan 18 '19 at 12:36

1

I solved the problem. In Home Ubuntu, I deleted the .gradle folder and downloaded it again. I hope it is useful

answered Jan 18 '19 at 12:36

HOSHYAR Ahmadpour

309
4
5

score 1 · Answer 12 · answered Dec 28 '19 at 10:46

1

Go to File->Other Settings->Preferences for New Projects->Build, Execution, Deployment->Build Tools->Gradle->Uncheck Offline work option.

answered Dec 28 '19 at 10:46

Collins USHI

567
7
17

2

The difference is between this "Default Settings" and this "Preferences for New Projects". I pretty sure you understand now – Collins USHI Dec 28 '19 at 11:29

score 0 · Answer 13 · answered Oct 02 '18 at 11:52

For users which have flavors in the project and found this thread:

Notice, that if your module dependency has different flavors, you should use one of the strategies:

Module that tightens dependencies should have the same flavors and dimensions as the dependency module
You should explicitly indicate which configuration you target in the module

Like that:

dependencies {
    compile project(path: ':module', configuration:'alphaDebug') 
}

score 0 · Answer 14 · answered Dec 16 '18 at 03:48

I ran into the same issue and adding mavenCentral() in the repositories block of my build.gradle file worked for me. I had Offline work unchecked and adding maven { url "https://maven.google.com" }. Adding this answer for the lost souls that find themselves at end of this thread.

score 0 · Answer 15 · answered Jan 21 '19 at 21:34

0

If you did not uncheck offline work, then make you sure you have internet for Android Studio to normalize your project.

answered Jan 21 '19 at 21:34

user2770352

89
7

score 0 · Answer 16 · answered Feb 20 '19 at 12:07

0

If you are getting this same error after adding dynamic module then don't worry follow this:

Add productFlavors in your build.gradle(dynamic- module)

productFlavors {
flavorDimensions "default"
stage {
   // to do
}
prod {
   // to do

 }
}

answered Feb 20 '19 at 12:07

Sandeep Sankla

1,250
12
21

score 0 · Answer 17 · answered Aug 01 '19 at 17:53

For other people where the accepted answer does not solve this issue...

As of September 2018, AndroidX has replaced the Android Support Libraries, which includes the appcompat-v7 library.

'com.android.support:appcompat-v7' becomes 'androidx.appcompat:appcompat:1.0.0'

'com.android.support:design' becomes 'com.google.android.material:material:1.0.0'

References:

https://developer.android.com/jetpack/androidx/migrate List of Support Libraries to AndroidX mappings

score 0 · Answer 18 · answered Jan 25 '20 at 09:45

0

For me the cause was incorrect url for jcenter. To solve it I simply changed url for app and proect level build.gradle

from

jcenter { url "http://jcenter.bintray.com/"}

to

jcenter()

answered Jan 25 '20 at 09:45

Marek

3,555
17
74
123

score 0 · Answer 19 · answered Feb 01 '20 at 05:53

0

Go to build.Gradle file and replace 27 and 29 by 25 at these places 1. targetSdkVersion 25 2. implementation 'com.android.support:appcompat-v7:25.+'

it really works for me Thanks.

answered Feb 01 '20 at 05:53

lovekesh madaan

21
2

score 0 · Answer 20 · answered Mar 14 '20 at 13:42

0

Used implementation 'androidx.appcompat:appcompat:1.1.2' in App gradle fixed the issue for me

answered Mar 14 '20 at 13:42

user3215178

13
2

Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.android.support:appcompat-v7:26.1.0

Error log:

20 Answers20

If above workaround not works then try this:

Manifest Declaration Changes

Following Android Developer Library Support.

`Invalidate Cache / Restart` from File option.

For users which have flavors in the project and found this thread:

Linked

Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.android.support:appcompat-v7:26.1.0

Error log:

20 Answers20

If above workaround not works then try this:

Manifest Declaration Changes

Following Android Developer Library Support.

Invalidate Cache / Restart from File option.

For users which have flavors in the project and found this thread:

Linked

`Invalidate Cache / Restart` from File option.