Unable to get dependencies from jcenter with a new project [closed]
I'm unable to get kotlin pom from jcenter with a new project.
All I have done is gone File->New Project and created a new project with no activity.
I'm getting the following error when it tries to build:
ERROR: Could not GET 'https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-stdlib-jdk8/1.3.21/kotlin-stdlib-jdk8-1.3.21.pom'. Received status code 502 from server: Bad Gateway Enable Gradle 'offline mode' and sync project
My build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:3.3.2'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
google()
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
If I go in my web browser to that URL I can't connect either. https://jcenter.bintray.com/
Does this mean the site is temporarily down or is there something I need to add to my build files?
BTW I selected Java for the project and not Kotlin on setup if that matters so not even sure why it's trying to get kotlin stuff.
android android-gradle jcenter
closed as off-topic by Cody Gray♦ Mar 25 at 3:14
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Cody Gray
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
I'm unable to get kotlin pom from jcenter with a new project.
All I have done is gone File->New Project and created a new project with no activity.
I'm getting the following error when it tries to build:
ERROR: Could not GET 'https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-stdlib-jdk8/1.3.21/kotlin-stdlib-jdk8-1.3.21.pom'. Received status code 502 from server: Bad Gateway Enable Gradle 'offline mode' and sync project
My build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:3.3.2'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
google()
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
If I go in my web browser to that URL I can't connect either. https://jcenter.bintray.com/
Does this mean the site is temporarily down or is there something I need to add to my build files?
BTW I selected Java for the project and not Kotlin on setup if that matters so not even sure why it's trying to get kotlin stuff.
android android-gradle jcenter
closed as off-topic by Cody Gray♦ Mar 25 at 3:14
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Cody Gray
If this question can be reworded to fit the rules in the help center, please edit the question.
I'm experiencing this as well and thought it was very weird. Since I'm not the only one, I'm thinking it may be temporary
– Chisko
Mar 21 at 8:35
maybe we should not upgrade the gradle to 3.3.2 yet
– Alfred Angkasa
Mar 21 at 8:46
add a comment |
I'm unable to get kotlin pom from jcenter with a new project.
All I have done is gone File->New Project and created a new project with no activity.
I'm getting the following error when it tries to build:
ERROR: Could not GET 'https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-stdlib-jdk8/1.3.21/kotlin-stdlib-jdk8-1.3.21.pom'. Received status code 502 from server: Bad Gateway Enable Gradle 'offline mode' and sync project
My build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:3.3.2'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
google()
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
If I go in my web browser to that URL I can't connect either. https://jcenter.bintray.com/
Does this mean the site is temporarily down or is there something I need to add to my build files?
BTW I selected Java for the project and not Kotlin on setup if that matters so not even sure why it's trying to get kotlin stuff.
android android-gradle jcenter
I'm unable to get kotlin pom from jcenter with a new project.
All I have done is gone File->New Project and created a new project with no activity.
I'm getting the following error when it tries to build:
ERROR: Could not GET 'https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-stdlib-jdk8/1.3.21/kotlin-stdlib-jdk8-1.3.21.pom'. Received status code 502 from server: Bad Gateway Enable Gradle 'offline mode' and sync project
My build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:3.3.2'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
google()
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
If I go in my web browser to that URL I can't connect either. https://jcenter.bintray.com/
Does this mean the site is temporarily down or is there something I need to add to my build files?
BTW I selected Java for the project and not Kotlin on setup if that matters so not even sure why it's trying to get kotlin stuff.
android android-gradle jcenter
android android-gradle jcenter
edited Mar 21 at 11:28
ישו אוהב אותך
16.3k84260
16.3k84260
asked Mar 21 at 8:24
user8810083user8810083
274112
274112
closed as off-topic by Cody Gray♦ Mar 25 at 3:14
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Cody Gray
If this question can be reworded to fit the rules in the help center, please edit the question.
closed as off-topic by Cody Gray♦ Mar 25 at 3:14
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Cody Gray
If this question can be reworded to fit the rules in the help center, please edit the question.
I'm experiencing this as well and thought it was very weird. Since I'm not the only one, I'm thinking it may be temporary
– Chisko
Mar 21 at 8:35
maybe we should not upgrade the gradle to 3.3.2 yet
– Alfred Angkasa
Mar 21 at 8:46
add a comment |
I'm experiencing this as well and thought it was very weird. Since I'm not the only one, I'm thinking it may be temporary
– Chisko
Mar 21 at 8:35
maybe we should not upgrade the gradle to 3.3.2 yet
– Alfred Angkasa
Mar 21 at 8:46
I'm experiencing this as well and thought it was very weird. Since I'm not the only one, I'm thinking it may be temporary
– Chisko
Mar 21 at 8:35
I'm experiencing this as well and thought it was very weird. Since I'm not the only one, I'm thinking it may be temporary
– Chisko
Mar 21 at 8:35
maybe we should not upgrade the gradle to 3.3.2 yet
– Alfred Angkasa
Mar 21 at 8:46
maybe we should not upgrade the gradle to 3.3.2 yet
– Alfred Angkasa
Mar 21 at 8:46
add a comment |
10 Answers
10
active
oldest
votes
jcenter is currently down. In the end adding mavenCentral()
to both sets of repositories in the project build.gradle
file worked as a workaround for me:
buildscript {
repositories {
mavenCentral()
google()
jcenter()
...
allprojects {
repositories {
mavenCentral()
google()
jcenter()
...
Not working for me.
– MateenSheikh
Mar 21 at 9:23
@MateenSheikh , do you still get the same error? What does your build file look like?
– user8810083
Mar 21 at 10:32
@user8810083 jcenter is working fine now so issue is resolved.
– MateenSheikh
Mar 21 at 12:34
add a comment |
Downgrade Gradle version is not a good fix for me. I did google around and found this. Jcenter is dead. For now.
https://status.bintray.com/?fbclid=IwAR3NLsnuGA5xqbFhcPsVLWX2c9TG40JWQcDYM7RTVsDm0qDSQvfjmhabhPg
I think all we can do is wait.
1
see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:11
The server is broken! I did a completely fresh install of android studio and can't create a new project
– Benjamin
Mar 21 at 9:13
@Benjamin , adding mavenCentral as repository is a workaround for now
– user8810083
Mar 21 at 10:33
add a comment |
While mostly meant as a temporary, change-back-again-when-jcenter-is-working solution, this can be fixed by downgrading the gradle plugin version to 3.3.1 in the project's gradle file:
classpath 'com.android.tools.build:gradle:3.3.1'
@Chisko I'm still getting the same error as OP
– Saurabh
Mar 21 at 9:04
this didn't work for me, but see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:09
this gives me a read timeout error.
– Vikas Kumar
Mar 21 at 9:49
add a comment |
There is a problem in Downloads
section with Partial Outage
in jfrog bintray (https://status.bintray.com/incidents/2wvx6d5f807c):
Intermittent download issues in Bintray
You can see the current status in https://status.bintray.com/
Update Status from jfrog Bintray:
Update - There are still intermittent download issues in Oregon region (north America). We are still working on identifying the root cause.
Mar 21, 10:02 UTC
add a comment |
Add this to dependencies
block
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.21"
Maybe the OP doesn't need Kotlin support
– Chisko
Mar 21 at 9:02
add a comment |
replace jcenter() with mavenCentral()
because jcenter is not available now
add a comment |
Actually android studio already had the solution for you :
Syncing only active variant
You can disable this experimental feature from
File → Settings → Experimental → Gradle → Only sync the active variant
add a comment |
I have same issue, and I tried aliyun maven in this issue's answer,
jcenter 502 bad gateway after gradle refresh
and it works. So I temporary use this for building app.
add a comment |
To fix it open android sdk manager and:
1.Uninstall android support repository
2.Install again android support repository
3.clean project and rebuild it
add a comment |
It's 3 days later and i was still getting random 502 errors from bintray, for links that seemed perfectly valid. Manually checking with browser / curl the pom files were there.
What eventually helped get around, was slowing gradle down by not letting it hit the links all at once. In my case, cordova/ionic project, so
ionic cordova run android -- -- --gradleArg=--max-workers=1
Passing --no-parallel
should work as well
add a comment |
10 Answers
10
active
oldest
votes
10 Answers
10
active
oldest
votes
active
oldest
votes
active
oldest
votes
jcenter is currently down. In the end adding mavenCentral()
to both sets of repositories in the project build.gradle
file worked as a workaround for me:
buildscript {
repositories {
mavenCentral()
google()
jcenter()
...
allprojects {
repositories {
mavenCentral()
google()
jcenter()
...
Not working for me.
– MateenSheikh
Mar 21 at 9:23
@MateenSheikh , do you still get the same error? What does your build file look like?
– user8810083
Mar 21 at 10:32
@user8810083 jcenter is working fine now so issue is resolved.
– MateenSheikh
Mar 21 at 12:34
add a comment |
jcenter is currently down. In the end adding mavenCentral()
to both sets of repositories in the project build.gradle
file worked as a workaround for me:
buildscript {
repositories {
mavenCentral()
google()
jcenter()
...
allprojects {
repositories {
mavenCentral()
google()
jcenter()
...
Not working for me.
– MateenSheikh
Mar 21 at 9:23
@MateenSheikh , do you still get the same error? What does your build file look like?
– user8810083
Mar 21 at 10:32
@user8810083 jcenter is working fine now so issue is resolved.
– MateenSheikh
Mar 21 at 12:34
add a comment |
jcenter is currently down. In the end adding mavenCentral()
to both sets of repositories in the project build.gradle
file worked as a workaround for me:
buildscript {
repositories {
mavenCentral()
google()
jcenter()
...
allprojects {
repositories {
mavenCentral()
google()
jcenter()
...
jcenter is currently down. In the end adding mavenCentral()
to both sets of repositories in the project build.gradle
file worked as a workaround for me:
buildscript {
repositories {
mavenCentral()
google()
jcenter()
...
allprojects {
repositories {
mavenCentral()
google()
jcenter()
...
edited Mar 21 at 11:29
ישו אוהב אותך
16.3k84260
16.3k84260
answered Mar 21 at 9:08
user8810083user8810083
274112
274112
Not working for me.
– MateenSheikh
Mar 21 at 9:23
@MateenSheikh , do you still get the same error? What does your build file look like?
– user8810083
Mar 21 at 10:32
@user8810083 jcenter is working fine now so issue is resolved.
– MateenSheikh
Mar 21 at 12:34
add a comment |
Not working for me.
– MateenSheikh
Mar 21 at 9:23
@MateenSheikh , do you still get the same error? What does your build file look like?
– user8810083
Mar 21 at 10:32
@user8810083 jcenter is working fine now so issue is resolved.
– MateenSheikh
Mar 21 at 12:34
Not working for me.
– MateenSheikh
Mar 21 at 9:23
Not working for me.
– MateenSheikh
Mar 21 at 9:23
@MateenSheikh , do you still get the same error? What does your build file look like?
– user8810083
Mar 21 at 10:32
@MateenSheikh , do you still get the same error? What does your build file look like?
– user8810083
Mar 21 at 10:32
@user8810083 jcenter is working fine now so issue is resolved.
– MateenSheikh
Mar 21 at 12:34
@user8810083 jcenter is working fine now so issue is resolved.
– MateenSheikh
Mar 21 at 12:34
add a comment |
Downgrade Gradle version is not a good fix for me. I did google around and found this. Jcenter is dead. For now.
https://status.bintray.com/?fbclid=IwAR3NLsnuGA5xqbFhcPsVLWX2c9TG40JWQcDYM7RTVsDm0qDSQvfjmhabhPg
I think all we can do is wait.
1
see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:11
The server is broken! I did a completely fresh install of android studio and can't create a new project
– Benjamin
Mar 21 at 9:13
@Benjamin , adding mavenCentral as repository is a workaround for now
– user8810083
Mar 21 at 10:33
add a comment |
Downgrade Gradle version is not a good fix for me. I did google around and found this. Jcenter is dead. For now.
https://status.bintray.com/?fbclid=IwAR3NLsnuGA5xqbFhcPsVLWX2c9TG40JWQcDYM7RTVsDm0qDSQvfjmhabhPg
I think all we can do is wait.
1
see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:11
The server is broken! I did a completely fresh install of android studio and can't create a new project
– Benjamin
Mar 21 at 9:13
@Benjamin , adding mavenCentral as repository is a workaround for now
– user8810083
Mar 21 at 10:33
add a comment |
Downgrade Gradle version is not a good fix for me. I did google around and found this. Jcenter is dead. For now.
https://status.bintray.com/?fbclid=IwAR3NLsnuGA5xqbFhcPsVLWX2c9TG40JWQcDYM7RTVsDm0qDSQvfjmhabhPg
I think all we can do is wait.
Downgrade Gradle version is not a good fix for me. I did google around and found this. Jcenter is dead. For now.
https://status.bintray.com/?fbclid=IwAR3NLsnuGA5xqbFhcPsVLWX2c9TG40JWQcDYM7RTVsDm0qDSQvfjmhabhPg
I think all we can do is wait.
answered Mar 21 at 9:09
Hau LuuHau Luu
2161315
2161315
1
see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:11
The server is broken! I did a completely fresh install of android studio and can't create a new project
– Benjamin
Mar 21 at 9:13
@Benjamin , adding mavenCentral as repository is a workaround for now
– user8810083
Mar 21 at 10:33
add a comment |
1
see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:11
The server is broken! I did a completely fresh install of android studio and can't create a new project
– Benjamin
Mar 21 at 9:13
@Benjamin , adding mavenCentral as repository is a workaround for now
– user8810083
Mar 21 at 10:33
1
1
see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:11
see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:11
The server is broken! I did a completely fresh install of android studio and can't create a new project
– Benjamin
Mar 21 at 9:13
The server is broken! I did a completely fresh install of android studio and can't create a new project
– Benjamin
Mar 21 at 9:13
@Benjamin , adding mavenCentral as repository is a workaround for now
– user8810083
Mar 21 at 10:33
@Benjamin , adding mavenCentral as repository is a workaround for now
– user8810083
Mar 21 at 10:33
add a comment |
While mostly meant as a temporary, change-back-again-when-jcenter-is-working solution, this can be fixed by downgrading the gradle plugin version to 3.3.1 in the project's gradle file:
classpath 'com.android.tools.build:gradle:3.3.1'
@Chisko I'm still getting the same error as OP
– Saurabh
Mar 21 at 9:04
this didn't work for me, but see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:09
this gives me a read timeout error.
– Vikas Kumar
Mar 21 at 9:49
add a comment |
While mostly meant as a temporary, change-back-again-when-jcenter-is-working solution, this can be fixed by downgrading the gradle plugin version to 3.3.1 in the project's gradle file:
classpath 'com.android.tools.build:gradle:3.3.1'
@Chisko I'm still getting the same error as OP
– Saurabh
Mar 21 at 9:04
this didn't work for me, but see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:09
this gives me a read timeout error.
– Vikas Kumar
Mar 21 at 9:49
add a comment |
While mostly meant as a temporary, change-back-again-when-jcenter-is-working solution, this can be fixed by downgrading the gradle plugin version to 3.3.1 in the project's gradle file:
classpath 'com.android.tools.build:gradle:3.3.1'
While mostly meant as a temporary, change-back-again-when-jcenter-is-working solution, this can be fixed by downgrading the gradle plugin version to 3.3.1 in the project's gradle file:
classpath 'com.android.tools.build:gradle:3.3.1'
edited Mar 24 at 11:50
E_net4
12.8k73872
12.8k73872
answered Mar 21 at 8:39
ChiskoChisko
1,96251835
1,96251835
@Chisko I'm still getting the same error as OP
– Saurabh
Mar 21 at 9:04
this didn't work for me, but see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:09
this gives me a read timeout error.
– Vikas Kumar
Mar 21 at 9:49
add a comment |
@Chisko I'm still getting the same error as OP
– Saurabh
Mar 21 at 9:04
this didn't work for me, but see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:09
this gives me a read timeout error.
– Vikas Kumar
Mar 21 at 9:49
@Chisko I'm still getting the same error as OP
– Saurabh
Mar 21 at 9:04
@Chisko I'm still getting the same error as OP
– Saurabh
Mar 21 at 9:04
this didn't work for me, but see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:09
this didn't work for me, but see the answer I just posted. Just adding mavenCentral() to both sets of repositories works for me now
– user8810083
Mar 21 at 9:09
this gives me a read timeout error.
– Vikas Kumar
Mar 21 at 9:49
this gives me a read timeout error.
– Vikas Kumar
Mar 21 at 9:49
add a comment |
There is a problem in Downloads
section with Partial Outage
in jfrog bintray (https://status.bintray.com/incidents/2wvx6d5f807c):
Intermittent download issues in Bintray
You can see the current status in https://status.bintray.com/
Update Status from jfrog Bintray:
Update - There are still intermittent download issues in Oregon region (north America). We are still working on identifying the root cause.
Mar 21, 10:02 UTC
add a comment |
There is a problem in Downloads
section with Partial Outage
in jfrog bintray (https://status.bintray.com/incidents/2wvx6d5f807c):
Intermittent download issues in Bintray
You can see the current status in https://status.bintray.com/
Update Status from jfrog Bintray:
Update - There are still intermittent download issues in Oregon region (north America). We are still working on identifying the root cause.
Mar 21, 10:02 UTC
add a comment |
There is a problem in Downloads
section with Partial Outage
in jfrog bintray (https://status.bintray.com/incidents/2wvx6d5f807c):
Intermittent download issues in Bintray
You can see the current status in https://status.bintray.com/
Update Status from jfrog Bintray:
Update - There are still intermittent download issues in Oregon region (north America). We are still working on identifying the root cause.
Mar 21, 10:02 UTC
There is a problem in Downloads
section with Partial Outage
in jfrog bintray (https://status.bintray.com/incidents/2wvx6d5f807c):
Intermittent download issues in Bintray
You can see the current status in https://status.bintray.com/
Update Status from jfrog Bintray:
Update - There are still intermittent download issues in Oregon region (north America). We are still working on identifying the root cause.
Mar 21, 10:02 UTC
edited Mar 21 at 10:45
answered Mar 21 at 9:43
ישו אוהב אותךישו אוהב אותך
16.3k84260
16.3k84260
add a comment |
add a comment |
Add this to dependencies
block
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.21"
Maybe the OP doesn't need Kotlin support
– Chisko
Mar 21 at 9:02
add a comment |
Add this to dependencies
block
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.21"
Maybe the OP doesn't need Kotlin support
– Chisko
Mar 21 at 9:02
add a comment |
Add this to dependencies
block
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.21"
Add this to dependencies
block
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.21"
answered Mar 21 at 8:44
DemonickDemonick
1,52022231
1,52022231
Maybe the OP doesn't need Kotlin support
– Chisko
Mar 21 at 9:02
add a comment |
Maybe the OP doesn't need Kotlin support
– Chisko
Mar 21 at 9:02
Maybe the OP doesn't need Kotlin support
– Chisko
Mar 21 at 9:02
Maybe the OP doesn't need Kotlin support
– Chisko
Mar 21 at 9:02
add a comment |
replace jcenter() with mavenCentral()
because jcenter is not available now
add a comment |
replace jcenter() with mavenCentral()
because jcenter is not available now
add a comment |
replace jcenter() with mavenCentral()
because jcenter is not available now
replace jcenter() with mavenCentral()
because jcenter is not available now
answered Mar 21 at 9:54
MasterMaster
112
112
add a comment |
add a comment |
Actually android studio already had the solution for you :
Syncing only active variant
You can disable this experimental feature from
File → Settings → Experimental → Gradle → Only sync the active variant
add a comment |
Actually android studio already had the solution for you :
Syncing only active variant
You can disable this experimental feature from
File → Settings → Experimental → Gradle → Only sync the active variant
add a comment |
Actually android studio already had the solution for you :
Syncing only active variant
You can disable this experimental feature from
File → Settings → Experimental → Gradle → Only sync the active variant
Actually android studio already had the solution for you :
Syncing only active variant
You can disable this experimental feature from
File → Settings → Experimental → Gradle → Only sync the active variant
answered Mar 21 at 10:04
Ahmad Zuhair DzulfiqorAhmad Zuhair Dzulfiqor
111
111
add a comment |
add a comment |
I have same issue, and I tried aliyun maven in this issue's answer,
jcenter 502 bad gateway after gradle refresh
and it works. So I temporary use this for building app.
add a comment |
I have same issue, and I tried aliyun maven in this issue's answer,
jcenter 502 bad gateway after gradle refresh
and it works. So I temporary use this for building app.
add a comment |
I have same issue, and I tried aliyun maven in this issue's answer,
jcenter 502 bad gateway after gradle refresh
and it works. So I temporary use this for building app.
I have same issue, and I tried aliyun maven in this issue's answer,
jcenter 502 bad gateway after gradle refresh
and it works. So I temporary use this for building app.
edited Mar 22 at 2:53
answered Mar 21 at 10:57
TingTing
25126
25126
add a comment |
add a comment |
To fix it open android sdk manager and:
1.Uninstall android support repository
2.Install again android support repository
3.clean project and rebuild it
add a comment |
To fix it open android sdk manager and:
1.Uninstall android support repository
2.Install again android support repository
3.clean project and rebuild it
add a comment |
To fix it open android sdk manager and:
1.Uninstall android support repository
2.Install again android support repository
3.clean project and rebuild it
To fix it open android sdk manager and:
1.Uninstall android support repository
2.Install again android support repository
3.clean project and rebuild it
edited Mar 24 at 10:47
answered Mar 24 at 9:51
Rabiun IslamRabiun Islam
243
243
add a comment |
add a comment |
It's 3 days later and i was still getting random 502 errors from bintray, for links that seemed perfectly valid. Manually checking with browser / curl the pom files were there.
What eventually helped get around, was slowing gradle down by not letting it hit the links all at once. In my case, cordova/ionic project, so
ionic cordova run android -- -- --gradleArg=--max-workers=1
Passing --no-parallel
should work as well
add a comment |
It's 3 days later and i was still getting random 502 errors from bintray, for links that seemed perfectly valid. Manually checking with browser / curl the pom files were there.
What eventually helped get around, was slowing gradle down by not letting it hit the links all at once. In my case, cordova/ionic project, so
ionic cordova run android -- -- --gradleArg=--max-workers=1
Passing --no-parallel
should work as well
add a comment |
It's 3 days later and i was still getting random 502 errors from bintray, for links that seemed perfectly valid. Manually checking with browser / curl the pom files were there.
What eventually helped get around, was slowing gradle down by not letting it hit the links all at once. In my case, cordova/ionic project, so
ionic cordova run android -- -- --gradleArg=--max-workers=1
Passing --no-parallel
should work as well
It's 3 days later and i was still getting random 502 errors from bintray, for links that seemed perfectly valid. Manually checking with browser / curl the pom files were there.
What eventually helped get around, was slowing gradle down by not letting it hit the links all at once. In my case, cordova/ionic project, so
ionic cordova run android -- -- --gradleArg=--max-workers=1
Passing --no-parallel
should work as well
answered Mar 25 at 2:23
kertkert
1,3501117
1,3501117
add a comment |
add a comment |
I'm experiencing this as well and thought it was very weird. Since I'm not the only one, I'm thinking it may be temporary
– Chisko
Mar 21 at 8:35
maybe we should not upgrade the gradle to 3.3.2 yet
– Alfred Angkasa
Mar 21 at 8:46