Slackbot
11/03/2022, 2:11 AMVampire
11/03/2022, 2:36 AMRicardo Simon
11/03/2022, 2:53 AMThank you, but I already know the reason for the problem, it is that I am from Cuba and the server gave me the sanctions, thank you very much.
joschi
11/04/2022, 9:47 AMit is that I am from Cuba and the server gave me the sanctionsNo, in this case it is because JCenter (jcenter.bintray.com) has been decommissioned a while ago and your build still relies on it. See https://developer.android.com/studio/build/jcenter-migration.
joschi
11/04/2022, 9:48 AMVampire
11/04/2022, 10:11 AMjoschi
11/04/2022, 10:20 AM# curl -i <https://jcenter.bintray.com/com/android/tools/build/gradle/4.0.0/gradle-4.0.0.pom>
HTTP/2 404
via: 1.1 google
date: Fri, 04 Nov 2022 04:27:47 GMT
content-type: application/json;charset=ISO-8859-1
content-length: 88
age: 20946
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
{
"errors" : [ {
"status" : 404,
"message" : "Could not find resource"
} ]
}
Either way, migrating the build away from JCenter seems a good call…Vampire
11/04/2022, 10:26 AMThen maybe there's an outage right now?No, not another one. What you get is a 404, because it is neither on JCenter nor MavenCentral where it would forward to. In that case Gradle would look in the next defined repository which probably is
google()
in that build and that would have the requested dependency.
OP though gets 403 which is probably caused by him being in Cuba and in that case Gradle does not look further as it sees that as misconfiguration of user credentials for example.
Either way, migrating the build away from JCenter seems a good call…Definitely, but from what I see, I'd guess he didn't author that build but just want to run it. In some cases some tools that wrap Gradle calls also have some auto-generated Gradle project templates they use that use JCenter and where you cannot easily remove its usage and so on.