Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

401 on public repository #5704

Closed
humblehacker opened this issue Jun 22, 2023 · 11 comments
Closed

401 on public repository #5704

humblehacker opened this issue Jun 22, 2023 · 11 comments

Comments

@humblehacker
Copy link

Describe the bug
For the past few days, I've been getting a 401 trying to load a public dependency:

To Reproduce
Steps to reproduce the behavior:

  1. curl -I https://jitpack.io/net/cachapa/expandablelayout/expandablelayout/2.9.2/expandablelayout-2.9.2.pom

Expected behavior
Normal response to HEAD request

Observed behavior

HTTP/2 401
date: Thu, 22 Jun 2023 15:52:42 GMT
content-type: text/plain; charset=utf-8
content-length: 35
cf-ray: 7db5a8f2f932c49b-SEA
cf-cache-status: BYPASS
cache-control: no-cache, no-store, must-revalidate, private
expires: 0
vary: Accept-Encoding
www-authenticate: Basic realm="JitPack"
artifact: net.cachapa.expandablelayout:expandablelayout:2.9.2
pragma: no-cache
x-jp-cf: 1
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=3BtrK5ezVRkzKbcl8gzrPDgTXi%2FA1%2B2TIV6zeR5BOSOg1%2FdzNKbQ8h8qS%2FHRBhBgLqU%2Bp%2FPoXxDxNIXraX6sdVHIir9gxB7kW0VpYNgDfBVVo86CXD9ExwdqC24%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare

Screenshots
Screenshot 2023-06-22 at 8 42 30 AM

@Angelhandy
Copy link

Angelhandy commented Jun 22, 2023

@rackami
Copy link

rackami commented Jun 23, 2023

@jitpack-io can you help with this?

@puttonous
Copy link

same problem found. any workarounds/fixes?

@avaneeshtripathi
Copy link

avaneeshtripathi commented Jun 23, 2023

What's happening here! Builds are blocked. 😢

This isn't there anymore: https://www.jitpack.io/io/github/kobakei/ratethisapp/1.2.0/ratethisapp-1.2.0.pom

and a few others.

The only solution I see is: Upgrade the packages wherever possible. And the ones which are obsolete maybe fork them and update manually. Check the PR section, people must have already created PRs with fixes that arent merged.

@stonefarmer9
Copy link

Currently having the same issue , built fine locally and in appcenter on wednesday. Thursday through to today getting:

Could not resolve all files for configuration ':app:releaseRuntimeClasspath'.
Could not resolve com.github.barteksc:android-pdf-viewer:2.8.2.
Required by:
project :app > project :react-native-view-pdf

Could not resolve com.github.barteksc:android-pdf-viewer:2.8.2.
Could not get resource 'https://www.jitpack.io/com/github/barteksc/android-pdf-viewer/2.8.2/android-pdf-viewer-2.8.2.pom'.
Could not GET 'https://www.jitpack.io/com/github/barteksc/android-pdf-viewer/2.8.2/android-pdf-viewer-2.8.2.pom'. Received status code 401 from server: Unauthorized

Have used GradlePluginPortal and did not resolve the issue.

@manindertwin
Copy link

manindertwin commented Jun 23, 2023

@jitpack-io Any Updates on this? Getting this issue from yesterday for multiple libraries..
Some libraries are throwing 401
e.g. Could not resolve com.github.stfalcon:chatkit:0.2.0.

some more are throwing 404
e.g. Could not find com.beloo.widget:ChipsLayoutManager:0.3.7.

@PaulNeesham
Copy link

Having same issue for:
androidmads.library.qrgenearator:QRGenearator:1.0.4
and
com.github.barteksc:android-pdf-viewer:3.2.0-beta.1

@sp0rk
Copy link

sp0rk commented Jun 23, 2023

Same for
com.tonyodev.fetch2:fetch2:3.0.12
and
com.github.stfalcon:stfalcon-imageviewer:1.0.1

None of them seem to be available in other maven repos.
Guess we need to wait for Jitpack's response or statically import the dependencies in our projects.

@charliecook2
Copy link

It looks like it could be related to this: https://status.gradle.com/?utm_source=embed

@humblehacker
Copy link
Author

According to https://status.gradle.com/incidents/7x4wqd7zv715:

JCenter is now serving artifacts again.

Let's see if things go back to normal

@humblehacker
Copy link
Author

My builds are again succeeding. I'm closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants