Requests to http://repo1.maven.org/maven2/ return a 501 HTTPS - minecraft

I am trying to build a mod for my Minecraft server in 1.7.10, but when I tried to execute ./gradlew setupDecompWorkspace, I got the error below.
I went to forums to see if other people had experienced this, and some had but my research did not explain how to modify the code to use HTTPS instead of HTTP. Any advice is appreciated.
* What went wrong:
A problem occurred configuring root project 'Client (Forge)'.
> Could not resolve all dependencies for configuration ':classpath'.
> Could not resolve org.eclipse.equinox:common:[3.2.0,4.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:jobs:3.5.300-v20130429-1813
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:contenttype:3.4.200-v20130326-1255
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.equinox:preferences:3.5.100-v20130422-1538
> Failed to list versions for org.eclipse.equinox:common.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/equinox/common/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/equinox/common/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
> Could not resolve org.eclipse.equinox:preferences:[3.2.0,4.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:contenttype:3.4.200-v20130326-1255
> Failed to list versions for org.eclipse.equinox:preferences.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/equinox/preferences/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/equinox/preferences/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
> Could not resolve org.eclipse.equinox:registry:[3.2.0,4.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:contenttype:3.4.200-v20130326-1255
> Failed to list versions for org.eclipse.equinox:registry.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/equinox/registry/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/equinox/registry/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
> Could not resolve org.eclipse.core.runtime:compatibility:[3.1.0,4.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:resources:3.2.1-R32x_v20060914
> Failed to list versions for org.eclipse.core.runtime:compatibility.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/core/runtime/compatibility/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/core/runtime/compatibility/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
> Could not resolve org.eclipse.core:expressions:[3.1.0,4.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:resources:3.2.1-R32x_v20060914
> Failed to list versions for org.eclipse.core:expressions.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/core/expressions/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/core/expressions/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
> Could not resolve org.eclipse.core:filesystem:[1.0.0,2.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:resources:3.2.1-R32x_v20060914
> Failed to list versions for org.eclipse.core:filesystem.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/core/filesystem/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/core/filesystem/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
> Could not resolve org.eclipse:osgi:[3.7.0,4.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:runtime:3.9.0-v20130326-1255
> Failed to list versions for org.eclipse:osgi.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/osgi/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/osgi/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
> Could not resolve org.eclipse.equinox:common:[3.6.100,4.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:runtime:3.9.0-v20130326-1255
> Failed to list versions for org.eclipse.equinox:common.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/equinox/common/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/equinox/common/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
> Could not resolve org.eclipse.core:jobs:[3.2.0,4.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:runtime:3.9.0-v20130326-1255
> Failed to list versions for org.eclipse.core:jobs.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/core/jobs/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/core/jobs/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
> Could not resolve org.eclipse.equinox:registry:[3.4.0,4.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:runtime:3.9.0-v20130326-1255
> Failed to list versions for org.eclipse.equinox:registry.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/equinox/registry/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/equinox/registry/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
> Could not resolve org.eclipse.equinox:preferences:[3.4.0,4.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:runtime:3.9.0-v20130326-1255
> Failed to list versions for org.eclipse.equinox:preferences.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/equinox/preferences/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/equinox/preferences/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
> Could not resolve org.eclipse.core:contenttype:[3.3.0,4.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:runtime:3.9.0-v20130326-1255
> Failed to list versions for org.eclipse.core:contenttype.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/core/contenttype/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/core/contenttype/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
> Could not resolve org.eclipse.equinox:app:[1.0.0,2.0.0).
Required by:
:Client (Forge):unspecified > net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT > net.minecraftforge.srg2source:Srg2Source:3.2-SNAPSHOT > org.eclipse.core:runtime:3.9.0-v20130326-1255
> Failed to list versions for org.eclipse.equinox:app.
> Unable to load Maven meta-data from http://repo1.maven.org/maven2/org/eclipse/equinox/app/maven-metadata.xml.
> Could not GET 'http://repo1.maven.org/maven2/org/eclipse/equinox/app/maven-metadata.xml'. Received status code 501 from server: HTTPS Required
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED```

I found a solution for this a few months ago here
// The comments with [HTTPS FIX] tag refers to the parts that fixes the issue.
buildscript {
repositories {
// [HTTPS FIX] Replace mavenCentral() with the code block below
maven {
url "https://repo1.maven.org/maven2"
}
maven {
name = "forge"
url = "http://files.minecraftforge.net/maven"
}
maven {
name = "sonatype"
url = "https://oss.sonatype.org/content/repositories/snapshots/"
}
}
dependencies {
classpath 'net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT'
}
}
// [HTTPS FIX] Add the code block below
allprojects {
repositories {
all { ArtifactRepository repo ->
if (repo instanceof MavenArtifactRepository){
if (repo.url.toString().startsWith("http://repo1.maven.org/maven2")) {
repo.url = repo.url.toString().replace("http://", "https://")
}
}
}
}
}
apply plugin: 'forge'
version = "1.0"
group= "com.yourname.modid" // http://maven.apache.org/guides/mini/guide-naming-conventions.html
archivesBaseName = "modid"
minecraft {
version = "1.7.10-10.13.4.1558-1.7.10"
runDir = "eclipse"
}
dependencies {
}
processResources
{
// this will ensure that this task is redone when the versions change.
inputs.property "version", project.version
inputs.property "mcversion", project.minecraft.version
// replace stuff in mcmod.info, nothing else
from(sourceSets.main.resources.srcDirs) {
include 'mcmod.info'
// replace version and mcversion
expand 'version':project.version, 'mcversion':project.minecraft.version
}
// copy everything else, thats not the mcmod.info
from(sourceSets.main.resources.srcDirs) {
exclude 'mcmod.info'
}
}

In your build.gradle file, replace http://repo1.maven.org with https://repo1.maven.org.

Related

dependency url keeps getting appened to the end of our nexus respository

Migrated to Kotlin .kts and now I'm getting some build issues.
These are some of the errors:
> Could not resolve all files for configuration ':app:stagingNewDesignDebugRuntimeClasspath'.
> Could not resolve com.pierfrancescosoffritti.androidyoutubeplayer:core:10.0.5.
Required by:
project :app
> Could not resolve com.pierfrancescosoffritti.androidyoutubeplayer:core:10.0.5.
> Could not get resource 'https://nexus.central.tech/repository/nexus-releases/com/pierfrancescosoffritti/androidyoutubeplayer/core/10.0.5/core-10.0.5.pom'.
> Could not HEAD 'https://nexus.central.tech/repository/nexus-releases/com/pierfrancescosoffritti/androidyoutubeplayer/core/10.0.5/core-10.0.5.pom'. Received status code 401 from server: Unauthorized
> Could not resolve com.pierfrancescosoffritti.androidyoutubeplayer:core:10.0.5.
> Could not get resource 'https://s3.amazonaws.com/salesforcesos.com/android/maven/release/com/pierfrancescosoffritti/androidyoutubeplayer/core/10.0.5/core-10.0.5.pom'.
What I don't understand is that the dependency being appended to our Nexus server.
Could not resolve com.pierfrancescosoffritti.androidyoutubeplayer:core:10.0.5.
> Could not get resource 'https://nexus.central.tech/repository/nexus-releases/com/pierfrancescosoffritti/androidyoutubeplayer/core/10.0.5/core-10.0.5.pom
Our Nexus repository is https://nexus.central.tech/repository/nexus-releases
But /com/pierfrancescosoffritti/androidyoutubeplayer/core/10.0.5/core-10.0.5.pom keeps getting appended to it. And that is why it can't find the full path and the build will fail.
androidyoutubeplayer doesn't come from our Nexus so I don't understand why it's trying to get it from there.
// build.gradle.kts
repositories {
google()
mavenCentral()
maven {
url = uri(properties["nexusRepositoryUrl"].toString())
credentials {
username = properties["nexusRepositoryUsername"].toString()
username = properties["nexusRepositoryPassword"].toString()
}
}
maven { url = uri("https://www.jitpack.io") }
maven { url = uri("https://s3.amazonaws.com/salesforcesos.com/android/maven/release") }
maven { url = uri("https://dl.bintray.com/objectbox/objectbox") }
maven { url = uri("https://sdk.uxcam.com/android/") }
}
UPDATE -- after correcting the username/password
Could not determine the dependencies of task ':app:compileUatDebugKotlin'.
> Could not resolve all files for configuration ':app:stagingNewDesignDebugRuntimeClasspath'.
> Could not resolve com.pierfrancescosoffritti.androidyoutubeplayer:core:10.0.5.
Required by:
project :app
> Skipped due to earlier error
> Could not resolve com.pierfrancescosoffritti.androidyoutubeplayer:core:10.0.5.
> Could not get resource 'https://s3.amazonaws.com/salesforcesos.com/android/maven/release/com/pierfrancescosoffritti/androidyoutubeplayer/core/10.0.5/core-10.0.5.pom'.
> Could not HEAD 'https://s3.amazonaws.com/salesforcesos.com/android/maven/release/com/pierfrancescosoffritti/androidyoutubeplayer/core/10.0.5/core-10.0.5.pom'. Received status code 403 from server: Forbidden
After looking at the git repo for androidyoutubeplayer. It should fetch that dependency from mavenCentral(). So Not sure why its looking at the above.
=== UPDATE 2 ===
jcenter() was removed originally, but I have put it back as we have some libraries that are old from there that haven't found their way to mavenCentral(). That was why some of the dependencies could not be found. So it was continue to search the other repositories.
This is build.gradle.kts
repositories {
google()
jcenter()
mavenCentral()
maven {
url = uri(properties["nexusRepositoryUrl"].toString())
credentials {
username = properties["nexusRepositoryUsername"].toString()
password = properties["nexusRepositoryPassword"].toString()
/* TODO: Remove after debugging */
println("USERNAME: $username")
println("PASSWORD: $password")
println("URL: $url")
}
}
maven { url = uri("https://sdk.uxcam.com/android/") }
maven { url = uri("https://www.jitpack.io") }
maven { url = uri("https://s3.amazonaws.com/salesforcesos.com/android/maven/release") }
maven { url = uri("https://dl.bintray.com/objectbox/objectbox") }
}
And this is the build.gradle (working ok)
repositories {
google()
jcenter()
mavenCentral()
maven {
url nexusRepositoryUrl
credentials {
username nexusRepositoryUsername
password nexusRepositoryPassword
}
}
maven { url 'https://sdk.uxcam.com/android/'}
maven { url "https://www.jitpack.io" }
maven { url 'https://s3.amazonaws.com/salesforcesos.com/android/maven/release' }
maven { url "https://dl.bintray.com/objectbox/objectbox" }
}
The errors are different now. This is what I get when building:
.gradle/caches/transforms-2/files-2.1/8fc5090e854d3eadc13743a6b4942213/jetified-kotlin-stdlib-1.6.0.jar!/META-INF/kotlin-stdlib.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.4.2.
.gradle/caches/transforms-2/files-2.1/bdaa895e8cd4dd25cc3b271fb1f2fc8e/jetified-kotlin-stdlib-jdk7-1.6.0.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.4.2.
.gradle/caches/transforms-2/files-2.1/cebf6956c831e2c0ba58bc90c4d45ce7/jetified-kotlin-stdlib-common-1.6.0.jar!/META-INF/kotlin-stdlib-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.4.2.
.gradle/caches/transforms-2/files-2.1/e0c09723c14595670dad4b40acbe2360/jetified-core-11.0.1-api.jar!/META-INF/core_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.4.2.
.gradle/caches/transforms-2/files-2.1/ec9cde959f0fd7b7d9fe2427414ce447/jetified-kotlin-stdlib-jdk8-1.6.0.jar!/META-INF/kotlin-stdlib-jdk8.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.4.2.
This is my project level build.gradle.kts
buildscript {
val kotlin_version = "1.4.32"
val navigationVersion = "2.3.5"
val objectboxVersion = "2.9.1"
val jacocoVersion = "0.8.5"
val sonarVersion = "3.0"
val newRelicVersion = "5.28.1"
repositories {
google()
mavenCentral()
}
dependencies {
classpath("com.android.tools.build:gradle:4.2.2")
classpath("org.jetbrains.kotlin:kotlin-gradle-plugin:")
classpath("org.jetbrains.kotlin:kotlin-noarg:$kotlin_version")
classpath("org.jacoco:org.jacoco.core:$jacocoVersion")
classpath("org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:$sonarVersion")
classpath("androidx.navigation:navigation-safe-args-gradle-plugin:$navigationVersion")
classpath("com.google.gms:google-services:4.3.8")
classpath("com.google.firebase:perf-plugin:1.3.4")
classpath("com.google.firebase:firebase-appdistribution-gradle:2.0.1")
classpath("com.google.firebase:firebase-crashlytics-gradle:2.4.1")
classpath("io.objectbox:objectbox-gradle-plugin:$objectboxVersion")
classpath("com.newrelic.agent.android:agent-gradle-plugin:$newRelicVersion")
classpath("com.akaita.android:easylauncher:1.3.1")
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
What I don't understand the build.gradle before migration works fine and all the versions of kotlin and dependencies are the same. As I have it on another branch.
When running the following command ./gradlew assembleUat --info
Failed to get resource: GET. [HTTP HTTP/1.1 403 Forbidden: https://s3.amazonaws.com/salesforcesos.com/android/maven/release/com/google/firebase/firebase-messaging/maven-metadata.xml)]
Failed to get resource: GET. [HTTP HTTP/1.1 502 Bad Gateway: https://dl.bintray.com/objectbox/objectbox/com/google/firebase/firebase-messaging/maven-metadata.xml)]
Failed to get resource: GET. [HTTP HTTP/1.1 502 Bad Gateway: https://dl.bintray.com/objectbox/objectbox/com/google/firebase/firebase-messaging/maven-metadata.xml)]
Failed to get resource: GET. [HTTP HTTP/1.1 502 Bad Gateway: https://dl.bintray.com/objectbox/objectbox/com/google/firebase/firebase-messaging/maven-metadata.xml)]
Failed to get resource: GET. [HTTP HTTP/1.1 403 Forbidden: https://s3.amazonaws.com/salesforcesos.com/android/maven/release/com/google/android/gms/play-services-location/maven-metadata.xml)]
Failed to get resource: GET. [HTTP HTTP/1.1 403 Forbidden: https://s3.amazonaws.com/salesforcesos.com/android/maven/release/com/google/android/gms/play-services-ads-identifier/maven-metadata.xml)]
Failed to get resource: GET. [HTTP HTTP/1.1 403 Forbidden: https://s3.amazonaws.com/salesforcesos.com/android/maven/release/com/google/android/gms/play-services-base/maven-metadata.xml)]
Failed to get resource: GET. [HTTP HTTP/1.1 403 Forbidden: https://s3.amazonaws.com/salesforcesos.com/android/maven/release/com/akamai/android/aka-common/maven-metadata.xml)]
The Gradle errors when it can't locate files in repositories are often confusing. What is important though is it says
Received status code 401 from server: Unauthorized.
Gradle doesn't know what artifact is stored in which repository, so it searches all of them for the .pom definition - but it fails because the username and password are incorrect.
I suspect that if you add some debug log statements, you'll see something unexpected.
// build.gradle.kts
credentials {
username = properties["nexusRepositoryUsername"].toString()
username = properties["nexusRepositoryPassword"].toString()
// ^^^ ^^^
println("repo user: $username")
println("repo pass: $password")
}
Of course, don't commit those to your repo!
Improvements
Aside from fixing the username/password mix-up, you can do more things to help out.
Use repository content filtering to tell Gradle what artifacts are stored in which repository.
Find the groups of the dependencies that you need to filter (I looked at the Salesforce docs to find them), and then configure the filtering in Gradle:
// build.gradle.kts
repositories {
maven {
url = uri(properties["nexusRepositoryUrl"].toString())
content {
// this repository *only* contains artifacts with the specified groups
includeGroup("com.salesforce.service")
includeGroup("com.salesforce.android")
}
}
// also filter 'objectbox' dependencies
maven("https://dl.bintray.com/objectbox/objectbox") {
content {
includeGroup("io.objectbox")
}
}
}
Now Gradle will only search for Salesforce artifacts in that repo.
As a nice side-effect, This will also improve performance, as Gradle won't bother searching that repo for unrelated artifacts.
Use 'named repository credentials' to automatically set the username/password based on the repository name.
See the answer here for a more thorough explanation of named repository credentials
// build.gradle.kts
repositories {
maven {
url = uri(properties["nexusRepositoryUrl"].toString())
name = "nexusRepository"
credentials(PasswordCredentials::class)
}
}
# $GRADLE_USER_HOME/gradle.properties
nexusRepositoryUsername=my-username
nexusRepositoryPassword=my-password
The solution was based on #aSemy comment. Which was to include only the dependencies that are needed for those repositories.
maven {
url = uri("https://s3.amazonaws.com/salesforcesos.com/android/maven/release")
content {
includeGroup("com.salesforce.service")
includeGroup("com.salesforce.android")
}
}
maven {
url = uri("https://dl.bintray.com/objectbox/objectbox")
content {
includeGroup("io.objectbox")
}
}

> Task :app:checkReleaseAarMetadata FAILED - React native

I am making a release build for my project using ./gradlew assembleRelease command but it gives me this error.
> Task :app:checkReleaseAarMetadata FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:checkReleaseAarMetadata'.
> Could not resolve all files for configuration ':app:releaseRuntimeClasspath'.
> Could not resolve com.facebook.android:facebook-android-sdk:[8,9).
Required by:
project :app
> Failed to list versions for com.facebook.android:facebook-android-sdk.
> Unable to load Maven meta-data from https://jcenter.bintray.com/com/facebook/android/facebook-android-sdk/maven-metadata.xml.
> Could not HEAD 'https://jcenter.bintray.com/com/facebook/android/facebook-android-sdk/maven-metadata.xml'.
> org.apache.http.client.ClientProtocolException (no error message)
my build.gradle
ext {
buildToolsVersion = "29.0.3"
minSdkVersion = 21
compileSdkVersion = 30
targetSdkVersion = 30
ndkVersion = "20.1.5948944"
googlePlayServicesAuthVersion = "16.0.1"
}
To solve this issue just change the compileSdkVersion in your build.gradle file.
Open android > build.gradle file.
Change compileSdkVersion from 29 to 30.
Change targetSdkVersion from 29 to 30.
now run again.
To solve this issue just add mavenCentral() in repositories of your project build.gradle.
Refer to https://developers.facebook.com/docs/android/getting-started/

Can not run-android because Could not parse POM https://dl.google.com/dl/android/maven2/android/arch/lifecycle/runtime/1.1.1/runtime-1.1.1.pom

I have just downloaded fresh project using react-native init -project name-, but I cannot run it in my emulator (react-native run-android)
It shows this in command prompt:
info JS server already running.
info Building and installing the app on the device (cd android && gradlew.bat app:installDebug)...
> Task :app:preDebugBuild
[Fatal Error] runtime-1.1.1.pom:2:1: Content is not allowed in prolog.
[Fatal Error] runtime-1.1.1.pom:2:1: Content is not allowed in prolog.
[Fatal Error] common-1.1.1.pom:2:1: Content is not allowed in prolog.
[Fatal Error] common-1.1.1.pom:2:1: Content is not allowed in prolog.
[Fatal Error] runtime-1.1.1.pom:2:1: Content is not allowed in prolog.
[Fatal Error] runtime-1.1.1.pom:2:1: Content is not allowed in prolog.
[Fatal Error] common-1.1.1.pom:2:1: Content is not allowed in prolog.
[Fatal Error] common-1.1.1.pom:2:1: Content is not allowed in prolog.
> Task :app:preDebugBuild FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Could not resolve all files for configuration ':app:debugCompileClasspath'.
> Could not resolve android.arch.lifecycle:runtime:1.1.1.
Required by:
project :app > com.android.support:support-compat:28.0.0
> Could not resolve android.arch.lifecycle:runtime:1.1.1.
> Could not parse POM https://dl.google.com/dl/android/maven2/android/arch/lifecycle/runtime/1.1.1/runtime-1.1.1.pom
> Content is not allowed in prolog.
> Could not resolve android.arch.core:runtime:1.1.1.
Required by:
project :app > android.arch.lifecycle:livedata:1.1.1
project :app > android.arch.lifecycle:livedata-core:1.1.1
> Could not resolve android.arch.core:runtime:1.1.1.
> Could not parse POM https://dl.google.com/dl/android/maven2/android/arch/core/runtime/1.1.1/runtime-1.1.1.pom
> Content is not allowed in prolog.
> Could not resolve android.arch.core:common:1.1.1.
Required by:
project :app > android.arch.lifecycle:livedata:1.1.1
project :app > android.arch.lifecycle:livedata-core:1.1.1
> Could not resolve android.arch.core:common:1.1.1.
> Could not parse POM https://dl.google.com/dl/android/maven2/android/arch/core/common/1.1.1/common-1.1.1.pom
> Content is not allowed in prolog.
> Could not resolve android.arch.lifecycle:common:1.1.1.
Required by:
project :app > android.arch.lifecycle:livedata-core:1.1.1
> Could not resolve android.arch.lifecycle:common:1.1.1.
> Could not parse POM https://dl.google.com/dl/android/maven2/android/arch/lifecycle/common/1.1.1/common-1.1.1.pom
> Content is not allowed in prolog.
I have tried to change my build:gradle version 3.0.1, it will be another error so I assume I need to upgrade my build gradle or lower my react native version. Right now I am trying to update my android sdk from android studio.
This is my current build gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
ext {
buildToolsVersion = "28.0.3"
minSdkVersion = 16
compileSdkVersion = 28
targetSdkVersion = 28
supportLibVersion = "28.0.0"
}
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:3.3.0'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
mavenLocal()
google()
jcenter()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url "$rootDir/../node_modules/react-native/android"
}
}
}
What am I missing if I want to update my build gradle?

Error:Cause: org.gradle.internal.component.external.model.DefaultModuleComponentSelector

My gradle.build
file for simple module is:
buildscript {
ext {
springBootVersion = '1.4.3.RELEASE'
}
repositories {
mavenCentral()
}
dependencies {
classpath("org.springframework.boot:spring-boot-gradle-plugin:${springBootVersion}")
}
}
apply plugin: 'java'
apply plugin: 'eclipse'
apply plugin: 'org.springframework.boot'
jar {
baseName = 'client-app'
version = '0.0.1-SNAPSHOT'
}
sourceCompatibility = 1.8
targetCompatibility = 1.8
repositories {
mavenCentral()
}
dependencies {
compile('org.springframework.cloud:spring-cloud-starter-feign')
// https://mvnrepository.com/artifact/com.netflix.hystrix/hystrix-core
compile('org.springframework.cloud:spring-cloud-starter-hystrix')
compile("org.springframework.boot:spring-boot-starter-web"){
exclude group: 'org.springframework.boot', module: 'spring-boot-starter-logging'
}
compileOnly('org.projectlombok:lombok')
testCompile('org.springframework.boot:spring-boot-starter-test')
}
dependencyManagement {
imports {
mavenBom "org.springframework.cloud:spring-cloud-dependencies:Camden.BUILD-SNAPSHOT"
mavenBom "org.springframework.boot:spring-boot-starter-parent:${springBootVersion}"
}
}
It was working well until I closed the IDE (Intellij IDEA 2016) and reopened. I got error as below:
Error:Cause: org.gradle.internal.component.external.model.DefaultModuleComponentSelector
When I tried to run via cmd, then I got error below:
$ ./gradlew build
:client-app:compileJava
FAILURE: Build failed with an exception.
* What went wrong:
Could not resolve all dependencies for configuration 'detachedConfiguration2'.
> Could not resolve org.projectlombok:lombok:.
Required by:
hystrix-example:client-app:unspecified
> Failed to resolve imported Maven boms: Could not find org.springframework.cloud:spring-cloud-dependencies:Camden.BUILD-SNAPSHOT.
Searched in the following locations:
https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-dependencies/Camden.BUILD-SNAPSHOT/maven-metadata.xml
https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-dependencies/Camden.BUILD-SNAPSHOT/spring-cloud-dependencies-Camden.BUILD-SNAPSHOT.pom
https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-dependencies/Camden.BUILD-SNAPSHOT/spring-cloud-dependencies-Camden.BUILD-SNAPSHOT.pom
Required by:
hystrix-example:client-app:unspecified
> Could not find org.springframework.cloud:spring-cloud-starter-feign:.
Searched in the following locations:
https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-starter-feign//spring-cloud-starter-feign-.pom
https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-starter-feign//spring-cloud-starter-feign-.jar
Required by:
hystrix-example:client-app:unspecified
> Could not find org.springframework.cloud:spring-cloud-starter-hystrix:.
Searched in the following locations:
https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-starter-hystrix//spring-cloud-starter-hystrix-.pom
https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-starter-hystrix//spring-cloud-starter-hystrix-.jar
Required by:
hystrix-example:client-app:unspecified
> Could not find org.springframework.boot:spring-boot-starter-web:.
Searched in the following locations:
https://repo1.maven.org/maven2/org/springframework/boot/spring-boot-starter-web//spring-boot-starter-web-.pom
https://repo1.maven.org/maven2/org/springframework/boot/spring-boot-starter-web//spring-boot-starter-web-.jar
Required by:
hystrix-example:client-app:unspecified
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
Total time: 9.571 secs
I couldn't figure out the solution.
I already tried gradle build --refresh-dependencies but didn't work for me.
TIA for help.
Finally, I got solution at Issue #5564. :)
As #wilkinson mentioned in his response on that issue, projects are relying on Spring Boot's dependency management and version resolution is failing.
So, I explicitly specified the versions as:
dependencies {
compile('org.springframework.cloud:spring-cloud-starter-feign:1.2.3.RELEASE')
// https://mvnrepository.com/artifact/com.netflix.hystrix/hystrix-core
compile('org.springframework.cloud:spring-cloud-starter-hystrix:1.2.3.RELEASE')
compile("org.springframework.boot:spring-boot-starter-web:1.4.3.RELEASE"){
exclude group: 'org.springframework.boot', module: 'spring-boot-starter-logging'
}
compileOnly('org.projectlombok:lombok:1.16.12')
testCompile('org.springframework.boot:spring-boot-starter-test:1.4.3.RELEASE')
}
And it worked for me. :)

react-native TransformError when requiring a node_module that has a package.json with a babel config that specifies uninstalled plugin

I try to use the package es6-error in a react native app.
The packager fails with
[node-haste] Encountered an error while persisting cache:
> ReferenceError: Unknown plugin "add-module-exports" specified in "/home/jwerner/veloyo/veloyo/partner/node_modules/es6-error/package.json" at 0, attempted to resolve relative to "/home/jwerner/veloyo/veloyo/partner/node_modules/es6-error"
> at /home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/options/option-manager.js:220:17
> at Array.map (native)
> at Function.normalisePlugins (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/options/option-manager.js:196:20)
> at OptionManager.mergeOptions (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/options/option-manager.js:317:36)
> at OptionManager.addConfig (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/options/option-manager.js:248:10)
> at OptionManager.findConfigs (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/options/option-manager.js:460:30)
> at OptionManager.init (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/options/option-manager.js:502:12)
> at File.initOptions (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/index.js:243:89)
> at new File (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/index.js:159:72)
> TransformError: /home/jwerner/veloyo/veloyo/partner/node_modules/es6-error/lib/index.js: Unknown plugin "add-module-exports" specified in "/home/jwerner/veloyo/veloyo/partner/node_modules/es6-error/package.json" at 0, attempted to resolve relative to "/home/jwerner/veloyo/veloyo/partner/node_modules/es6-error"
[node-haste] Encountered an error while persisting cache:
> ReferenceError: Unknown plugin "add-module-exports" specified in "/home/jwerner/veloyo/veloyo/partner/node_modules/es6-error/package.json" at 0, attempted to resolve relative to "/home/jwerner/veloyo/veloyo/partner/node_modules/es6-error"
> at /home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/options/option-manager.js:220:17
> at Array.map (native)
> at Function.normalisePlugins (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/options/option-manager.js:196:20)
> at OptionManager.mergeOptions (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/options/option-manager.js:317:36)
> at OptionManager.addConfig (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/options/option-manager.js:248:10)
> at OptionManager.findConfigs (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/options/option-manager.js:460:30)
> at OptionManager.init (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/options/option-manager.js:502:12)
> at File.initOptions (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/index.js:243:89)
> at new File (/home/jwerner/veloyo/veloyo/partner/node_modules/babel-core/lib/transformation/file/index.js:159:72)
> TransformError: /home/jwerner/veloyo/veloyo/partner/node_modules/es6-error/lib/index.js: Unknown plugin "add-module-exports" specified in "/home/jwerner/veloyo/veloyo/partner/node_modules/es6-error/package.json" at 0, attempted to resolve relative to "/home/jwerner/veloyo/veloyo/partner/node_modules/es6-error"
The error seems to be that the es6-error specifies its babel configuration in its package.json.
While i found workarounds for the case that the package would have specified the babel config via .babelrc (post-install hook that deletes the given .babelrc files) i haven't been able to fix this error.
Any pointers?
My versions:
❯ react-native --version
react-native-cli: 0.1.10
react-native: 0.27.0-rc
❯ node -v
v5.1.1
❯ npm -v
3.8.3