-
Notifications
You must be signed in to change notification settings - Fork 173
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
Comments
Same problem other repository: https://www.jitpack.io/com/archit/calendar/awesome-calendar/1.1.4/awesome-calendar-1.1.4.pom |
@jitpack-io can you help with this? |
same problem found. any workarounds/fixes? |
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. |
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'.
Have used GradlePluginPortal and did not resolve the issue. |
@jitpack-io Any Updates on this? Getting this issue from yesterday for multiple libraries.. some more are throwing 404 |
Having same issue for: |
Same for None of them seem to be available in other maven repos. |
It looks like it could be related to this: https://status.gradle.com/?utm_source=embed |
According to https://status.gradle.com/incidents/7x4wqd7zv715:
Let's see if things go back to normal |
My builds are again succeeding. I'm closing this. |
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:
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
Screenshots
The text was updated successfully, but these errors were encountered: