Build fails (ArtifactResolveException)

Android app won’t build because of the issue as below:

Caused by: org.gradle.internal.resolve.ArtifactResolveException: Could not determine artifacts for com.github.ChuckerTeam.Chucker:library:3.0.1: Skipped due to earlier error
	at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ErrorHandlingModuleComponentRepository$ErrorHandlingModuleComponentRepositoryAccess.lambda$resolveArtifacts$13(
	at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ErrorHandlingModuleComponentRepository$ErrorHandlingModuleComponentRepositoryAccess.performOperationWithRetries(
	at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ErrorHandlingModuleComponentRepository$ErrorHandlingModuleComponentRepositoryAccess.resolveArtifacts(
	at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainArtifactResolver.resolveArtifacts(
	at org.gradle.internal.resolve.resolver.DefaultArtifactSelector.resolveArtifacts(
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.artifact.ResolvedArtifactsGraphVisitor.getArtifacts(
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.artifact.ResolvedArtifactsGraphVisitor.visitEdges(
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.CompositeDependencyGraphVisitor.visitEdges(
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.assembleResult(
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.resolve(
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.DefaultArtifactDependencyResolver.resolve(
	at org.gradle.api.internal.artifacts.ivyservice.DefaultConfigurationResolver.resolveGraph(
	at org.gradle.api.internal.artifacts.ivyservice.ShortCircuitEmptyConfigurationResolver.resolveGraph(
	at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver.resolveGraph(
	... 167 more
1 Like

Hello, same problem here since this morning. I did not change anything.

Same problem here. It’s retrieving a library from not sure if that’s related.

I contacted Bitrise support today regarding this issue. It appears to be related to Jitpack and they are waiting for a response from the Jitpack support team. In the meantime I created a temporary workaround. I created a branch on which I extracted all of the libraries that are downloaded from Jitpack and added them as separate modules. I also added a script on Bitrise that rebases the currently built branch onto my newly created one. That way my builds are succeeding and I don’t have to change anything in my code (except for adding a new branch). Maybe that would be an acceptable temporary solution for you (if you don’t have too many libraries from Jitpack).

This is really annoying and clearly an issue on the Bitrise side because everything work perfectly locally.
I am more and more irritated by Bitrise unreliability and lack of support (actually fixing issues, not telling us to fix things ourselves).

Same problem here.

same issue here (with com.github.yalantis:ucrop:2.2.2-native)

it seems that adding www to jitpack url does the trick (at least it fixed the issue for me)
maven { url "" }

1 Like

Hi there everyone!

Thanks for your patience in this matter :slight_smile:

@stan_he I’m really sorry for you feeling frustrated, please note that Jitpack is a 3rd party tool and thus outside of our hands, the issue is not really ours to fix (you can actually see on Jitpack’s github repo a number of recent discussions about this, such as this one: Origin Connection Time-out · Issue #3973 · jitpack/ · GitHub)
We have already contacted them and are waiting for their response, so we can only try and find workarounds in the meantime.

The reason your build works locally is because your computer already has the gradle cache dependencies downloaded, but since our Virtual Machines are created and destroyed in every single build, they do not amass the collection of dependencies over the years the way a physical computer does. If you were to delete your local gradle cache, you would experience the same issues locally as you do on Bitrise :smiley:

BUT! It seems that currently a workaround could be to add a www in the repo URL in the Gradle file:
maven { url "" }

So please try and see if this works :wink:


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.