Jitpack.io: 401 from public repository

Created on 31 Oct 2019  路  15Comments  路  Source: jitpack/jitpack.io

Getting a 401 unauthorised error on a public repo. This is not isolated to just this one repo as it happens with a few others as well

Could not determine the dependencies of task ':app:compileStagingReleaseJavaWithJavac'.
> Could not resolve all dependencies for configuration ':app:stagingReleaseRuntimeClasspath'.
   > Could not determine artifacts for com.github.BWMuller.EasyGallery:easygallery-core:0.0.3
      > Could not get resource 'https://jitpack.io/com/github/BWMuller/EasyGallery/easygallery-core/0.0.3/easygallery-core-0.0.3.aar'.
         > Could not HEAD 'https://jitpack.io/com/github/BWMuller/EasyGallery/easygallery-core/0.0.3/easygallery-core-0.0.3.aar'. Received status code 401 from server: Unauthorized

Most helpful comment

Hi all,

There was an issue connecting to GitHub at the time which made JitPack assume it was a private repository.

All 15 comments

Same issue with another public repo:

Cached resource https://www.jitpack.io/com/github/AlexTrotsenko/RxActivityResult/newExplicitIntent-SNAPSHOT/maven-metadata.xml is up-to-date (lastModified: Mon Oct 21 13:49:47 CEST 2019).
Cached resource https://www.jitpack.io/com/github/AlexTrotsenko/RxActivityResult/newExplicitIntent-SNAPSHOT/RxActivityResult-newExplicitIntent-087ed305fd-1.pom is up-to-date (lastModified: Mon Oct 21 13:49:47 CEST 2019).
FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:preFullDebugBuild'.
> Could not resolve all task dependencies for configuration ':app:fullDebugRuntimeClasspath'.
   > Could not resolve com.github.AlexTrotsenko:RxActivityResult:newExplicitIntent-SNAPSHOT.
     Required by:
         project :app > project :common
      > Could not resolve com.github.AlexTrotsenko:RxActivityResult:newExplicitIntent-SNAPSHOT.
         > Unable to load Maven meta-data from https://www.jitpack.io/com/github/AlexTrotsenko/RxActivityResult/newExplicitIntent-SNAPSHOT/maven-metadata.xml.
            > Could not HEAD 'https://www.jitpack.io/com/github/AlexTrotsenko/RxActivityResult/newExplicitIntent-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized

* Try:
Run with --debug option to get more log output. Run with --scan to get full insights.

* Exception is:
org.gradle.api.internal.tasks.TaskDependencyResolveException: Could not determine the dependencies of task ':app:preFullDebugBuild'.
    at org.gradle.api.internal.tasks.CachingTaskDependencyResolveContext.getDependencies(CachingTaskDependencyResolveContext.java:66)
...
    at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
Caused by: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all task dependencies for configuration ':app:fullDebugRuntimeClasspath'.
    at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.rethrowFailure(DefaultConfiguration.java:1054)
...
    at org.gradle.api.internal.tasks.CachingTaskDependencyResolveContext.getDependencies(CachingTaskDependencyResolveContext.java:64)
    ... 90 more
Caused by: org.gradle.internal.resolve.ModuleVersionResolveException: Could not resolve com.github.AlexTrotsenko:RxActivityResult:newExplicitIntent-SNAPSHOT.
Required by:
    project :app > project :common

@jitpack-io any ideas what is the root of the problem or how to work-around it meanwhile?

Seems the same as been at #3759

@stanma true it is the same but that was meant to have been fixed in March then already.

I'm seeing the same thing over in https://github.com/jitpack/jitpack.io/issues/4042

the same issue just happened

  > Could not resolve com.google.protobuf:protobuf-java:2.6.1.
     > Could not parse POM https://jcenter.bintray.com/com/google/protobuf/protobuf-java/2.6.1/protobuf-java-2.6.1.pom
        > Could not download google.pom (com.google:google:1)
           > Could not get resource 'http://maven.apiusage.com/repository/maven-public/com/google/google/1/google-1.pom'.
              > Could not HEAD 'http://maven.apiusage.com/repository/maven-public/com/google/google/1/google-1.pom'. Received status code 401 from server: Unauthorized
  > Could not resolve com.google.protobuf:protobuf-java:2.6.1.
     > Could not parse POM https://jcenter.bintray.com/com/google/protobuf/protobuf-java/2.6.1/protobuf-java-2.6.1.pom
        > Could not download google.pom (com.google:google:1)
           > Could not get resource 'http://maven.apiusage.com/repository/maven-public/com/google/google/1/google-1.pom'.
              > Could not HEAD 'http://maven.apiusage.com/repository/maven-public/com/google/google/1/google-1.pom'. Received status code 401 from server: Unauthorized
  > Could not resolve com.google.protobuf:protobuf-java:2.6.1.
     > Could not parse POM https://jcenter.bintray.com/com/google/protobuf/protobuf-java/2.6.1/protobuf-java-2.6.1.pom
        > Could not download google.pom (com.google:google:1)
           > Could not get resource 'http://maven.apiusage.com/repository/maven-public/com/google/google/1/google-1.pom'.
              > Could not HEAD 'http://maven.apiusage.com/repository/maven-public/com/google/google/1/google-1.pom'. Received status code 401 from server: Unauthorized
  > Could not resolve com.google.protobuf:protobuf-java:2.6.1.
     > Could not parse POM https://jcenter.bintray.com/com/google/protobuf/protobuf-java/2.6.1/protobuf-java-2.6.1.pom
        > Could not download google.pom (com.google:google:1)
           > Could not get resource 'http://maven.apiusage.com/repository/maven-public/com/google/google/1/google-1.pom'.
              > Could not HEAD 'http://maven.apiusage.com/repository/maven-public/com/google/google/1/google-1.pom'. Received status code 401 from server: Unauthorized

I am having the same issue on my public repo, even though I can download the files through my browser Gradle will fail at the unauthorized message.

I am trying to access 'https://jitpack.io/com/github/guthix/Jagex-ByteBuf/ff61704caa/Jagex-ByteBuf-ff61704caa.jar' on gradle version 5.6.4.

The same issue with my repo

ping @jitpack-io -- please have a look

I am having the same issue on my public repo, even though I can download the files through my browser Gradle will fail at the unauthorized message.

I am trying to access 'https://jitpack.io/com/github/guthix/Jagex-ByteBuf/ff61704caa/Jagex-ByteBuf-ff61704caa.jar' on gradle version 5.6.4.

FWIW, that is not the case for me. Our public artifacts return 401, both from gradle and a web browser, and both for jitpack.io and www.jitpack.io.

Hi all,

There was an issue connecting to GitHub at the time which made JitPack assume it was a private repository.

@jitpack-io seems this happened again?:

* What went wrong:
Could not determine the dependencies of task ':android:kaptForFDroidDebugKotlin'.
> Could not resolve all task dependencies for configuration ':android:kapt'.
   > Could not resolve com.github.hotchemi:permissionsdispatcher-processor:4.6.0.
     Required by:
         project :android
      > Could not resolve com.github.hotchemi:permissionsdispatcher-processor:4.6.0.
         > Could not get resource 'https://jitpack.io/com/github/hotchemi/permissionsdispatcher-processor/4.6.0/permissionsdispatcher-processor-4.6.0.pom'.
            > Could not GET 'https://jitpack.io/com/github/hotchemi/permissionsdispatcher-processor/4.6.0/permissionsdispatcher-processor-4.6.0.pom'. Received status code 401 from server: Unauthorized

@jitpack-io This is happening for me as well on a public repo

org.gradle.api.resources.ResourceException: Could not get resource 'https://jitpack.io/com/github/stephenc/jcip/jcip-annotations/1.0-1/jcip-annotations-1.0-1.pom'. 
org.gradle.internal.resource.transport.http.HttpErrorStatusCodeException: Could not GET 'https://jitpack.io/com/github/stephenc/jcip/jcip-annotations/1.0-1/jcip-annotations-1.0-1.pom'. Received status code 401 from server: Unauthorized | 聽
org.gradle.api.resources.ResourceException: Could not get resource 'https://jitpack.io/com/github/stephenc/jcip/jcip-annotations/1.0-1/jcip-annotations-1.0-1.pom'. | 聽
org.gradle.internal.resource.transport.http.HttpErrorStatusCodeException: Could not GET 'https://jitpack.io/com/github/stephenc/jcip/jcip-annotations/1.0-1/jcip-annotations-1.0-1.pom'. Received status code 401 from server: Unauthorized | 聽

This still occurs after one year.

[   +1 ms] > Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'.
[   +9 ms]    > Could not resolve com.github.phanirithvij:bubbles:1.2.1.
[   +2 ms]      Required by:
[   +2 ms]          project :app
[   +6 ms]       > Could not resolve com.github.phanirithvij:bubbles:1.2.1.
[   +1 ms]          > Could not get resource 'https://jitpack.io/com/github/phanirithvij/bubbles/1.2.1/bubbles-1.2.1.pom'.
[   +3 ms]             > Could not GET 'https://jitpack.io/com/github/phanirithvij/bubbles/1.2.1/bubbles-1.2.1.pom'. Received status code 401 from server: Unauthorized
[   +2 ms] * Try:

@jitpack-io This is happening for me as well on a public repo

org.gradle.api.resources.ResourceException: Could not get resource 'https://jitpack.io/com/github/stephenc/jcip/jcip-annotations/1.0-1/jcip-annotations-1.0-1.pom'. 
org.gradle.internal.resource.transport.http.HttpErrorStatusCodeException: Could not GET 'https://jitpack.io/com/github/stephenc/jcip/jcip-annotations/1.0-1/jcip-annotations-1.0-1.pom'. Received status code 401 from server: Unauthorized | 聽
org.gradle.api.resources.ResourceException: Could not get resource 'https://jitpack.io/com/github/stephenc/jcip/jcip-annotations/1.0-1/jcip-annotations-1.0-1.pom'. | 聽
org.gradle.internal.resource.transport.http.HttpErrorStatusCodeException: Could not GET 'https://jitpack.io/com/github/stephenc/jcip/jcip-annotations/1.0-1/jcip-annotations-1.0-1.pom'. Received status code 401 from server: Unauthorized | 聽

me too

I am also seeing this issue on a public repo.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ennru picture ennru  路  4Comments

Hala-Nearmotion picture Hala-Nearmotion  路  4Comments

rumatoest picture rumatoest  路  5Comments

hypest picture hypest  路  5Comments

bsideup picture bsideup  路  4Comments