-
Notifications
You must be signed in to change notification settings - Fork 194
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
Android Libraries fail to resolve with https://jitpack.io #4002
Comments
Currently jitpack accessed over jitpack.io doesn't return all required files for artifacts, it only returns POMs. Short investigation would suggest that its Cloudflare configuration is invalid, since jitpack.io goes through Cloudflare CDN. As a temporary workaround, to bypass CDN, we use www.jitpack.io, which goes straight to Jitpack's servers. See jitpack/jitpack.io#4002.
Take a look here: https://stackoverflow.com/a/52812651/3595288 |
@vasiledoe this SO issue has been raised on May 17th, 2018. The response is from October, 2018. This GitHub issue was created seven days ago. The StackOverflow question points to this... |
Hi, What is the error you are seeing when installing |
Using |
I had troubles with https://github.com/franmontiel/PersistentCookieJar too, I can test later to see if I can repro the issue. (Since it was an old lib, I forked it and included it in my source). I recall I did the fork because it wasn't working when used via Gradle to some developers; we didn't think of trying the www.jitpack vs. just jitpack back then. In any case, I think both jitpack.io and the github page should agree on what they recommend. Should users use
And
|
We're seeing issues with both www.jitpack.io and jitpack.io now... |
@mbwhite Can you run gradle with the '--info' flag as suggested above and please post the error message? Thanks! |
Has anyone figured out a workaround, been struggling with this for days, with both www.jitpack.io and jitpack.io now |
@geoffduong I'll step in here, in the interest of fixing this problem quickly. Here's the output I get for
Here's our apply plugin: 'groovy'
repositories {
mavenCentral()
maven {
url 'https://www.jitpack.io'
}
}
dependencies {
compile 'com.github.AbletonDevTools:jenkins-pipeline-mocks:0.7+'
compile 'org.codehaus.groovy:groovy-all:2.4.12'
testCompile 'junit:junit:4.12'
testCompile(
group: 'com.lesfurets',
name: 'jenkins-pipeline-unit',
version: '1.0',
)
}
sourceSets {
main {
groovy {
srcDirs = ['src', 'vars']
}
}
test {
groovy {
srcDirs = ['test']
}
}
} |
ping @jitpack-io, this issue is quite severe! |
Same issue here, dependency not downloading anymore from android studio.
|
Hey guys, we've encountered this issue an hour ago and the solution was to remove the previous workaround ('www') and move it to the bottom of the repository list. - |
it seems upgrading to gradle 3.5.1 (and latest android studio) fixed the problem... or maybe it's a coincidence |
Tried with Studio v3.5.1, android-gradle 3.5.1 and gradle 5.4.1, it failed with below error- Unable to load Maven meta-data from https://www.jitpack.io/com/github/xxx/xxx/dev-SNAPSHOT/maven-metadata.xml Worked when used Studio v3.5.1, android-gradle 3.4.1 and gradle 5.2.1 |
Sorry been distracted with other work... the issue is acknowledged at least in the issue @AlexTrotsenko mentions above... they have at least responded to somebody on twitter as wel. |
@helen-jiayuhan I don't see how this is related, but have you tried StackOverflow? In addition, try |
sorry it's just something stupid with my AndroidStudio.... It just need to close the project and restart... Got me crazy for a long time to find this solution... |
@geoffduong : I would like to reopen this issue. Today I just faced the same issue, can you please reopen it again. |
works! thank you |
in android studio2022.1.1 patch2 gradle plugin version 7.4.2 gradle version 7.5 also have this problem |
I also encountered a similar problem. I was able to download the dependencies yesterday, and I found this problem when I was working today. |
How was it solved? |
Describe the bug
If you have maven { url "https://jitpack.io" } as your resolving url, then Jitpack will only return the POM for the Android dependency causing the Gradle sync to fail. The workaround currently is to wipe the dependency from your cache and update the resolving url to maven { url "https://www.jitpack.io" }
To Reproduce
Steps to reproduce the behavior:
Expected behavior
POM, AAR, and sources.jar are all resolved for the dependency.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: