Builds are failing when downloading the Android app module dependencies for the first time

Bitrise Build Issue Report template

Description of the issue

Builds are failing when downloading the Android app module dependencies for the first time.

Environment:

Bitrise.io: stack Android & Docker on Ubuntu 16.04

If on Bitrise.io: which stack? If not on Bitrise.io: on what operating system? (Plus any other information you can share)

On Gradle build while downloading the app module dependencies.

E.g.: Git Clone v3.6.0

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : YES
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : YES/NO
  • Does the issue happen sporadically, or every time? : sporadically
  • Does upgrading the build Step to the latest version help? :NO
  • When did the issue start? :

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what bitrise.io will get when it does a git clone in the clean environment! If possible please note which sections you tried.

Local reproduction: Linux / Android (docker based) stack builds

Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( https://www.bitrise.io/cli )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: Running your build locally in Docker - Bitrise Docs .

Build log

Download https://jcenter.bintray.com/com/squareup/okio/okio/1.15.0/okio-1.15.0.pom
Download https://jcenter.bintray.com/com/squareup/okio/okio-parent/1.15.0/okio-parent-1.15.0.pom
Download https://jcenter.bintray.com/com/amazonaws/aws-android-sdk-core/2.10.0/aws-android-sdk-core-2.10.0.pom
:app:checkReleaseClasspath FAILED

FAILURE: Build failed with an exception.

  • What went wrong:
    Could not resolve all dependencies for configuration ‘:app:releaseCompileClasspath’.

Could not determine artifacts for com.github.instacart.truetime-android:library-extension-rx:3.4: Skipped due to earlier error

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

  • Exception is:
    org.gradle.api.artifacts.ResolveException: Could not resolve all dependencies for configuration ‘:app:releaseCompileClasspath’.
    at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver.wrapException(ErrorHandlingConfigurationResolver.java:96)
    at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver.resolveGraph(ErrorHandlingConfigurationResolver.java:68)
    at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$4.run(DefaultConfiguration.java:494)
    at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
    at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)

Hi @thread, can you please include a build URL we could take a look at?

Thanks, @thread, I believe I just discussed this with a teammate of yours on our chat.

In summary, the dependency that is failing to download for you guys is hosted on JitPack which service was having an intermittent outage for over a week. Unfortunately, this information isn’t displayed or noted by them anywhere, so it’s understandably confusing.

So this is a duplicate of this thread: Build fails (ArtifactResolveException)

And here you can find a thread with more info and possible workaround: https://github.com/jitpack/jitpack.io/issues/3973

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