Gradle fails to find dependencies while building the project
Asked by Mohamad Dakroub:

The dependencies still exist when performing a build with Gradle from my machine, here is bitbucket's error report and the missing dependencies:

```
Unzipping /root/.gradle/wrapper/dists/gradle-8.0.2-bin/14c943julo9117po2d0tvaqaam/gradle-8.0.2-bin.zip to /root/.gradle/wrapper/dists/gradle-8.0.2-bin/14c943julo9117po2d0tvaqaam
Set executable permissions for: /root/.gradle/wrapper/dists/gradle-8.0.2-bin/14c943julo9117po2d0tvaqaam/gradle-8.0.2/bin/gradle

Welcome to Gradle 8.0.2!

Here are the highlights of this release:
- Improvements to the Kotlin DSL
- Fine-grained parallelism from the first build with configuration cache
- Configurable Gradle user home cache cleanup

For more details see https://docs.gradle.org/8.0.2/release-notes.html

No Gradle daemons are running.
Starting a Gradle Daemon (subsequent builds will be faster)
Configuration cache is an incubating feature.
Configuration on demand is an incubating feature.
Calculating task graph as no configuration cache is available for tasks: getCommitMessages

> Task :$RAY_KEY_ALIASspacetesting:getCommitMessages
Generating release notes ($RAY_KEY_ALIASspacetesting/firebase-release-notes.txt)

0 problems were found storing the configuration cache.

See the complete report at file:///opt/atlassian/pipelines/agent/build/build/reports/configuration-cache/7q2onlupz2wbd21fosmnvh92w/5gjyplmws3ed909ia8d335k31/configuration-cache-report.html

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/8.0.2/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 47s
1 actionable task: 1 executed
Configuration cache entry stored.
Configuration cache is an incubating feature.
Configuration on demand is an incubating feature.
Calculating task graph as no configuration cache is available for tasks: :$RAY_KEY_ALIASspace:assembleDebug :$RAY_KEY_ALIASspace:appDistributionUploadDebug :$RAY_KEY_ALIASspacetesting:assembleDebug :$RAY_KEY_ALIASspacetesting:appDistributionUploadDebug

0 problems were found storing the configuration cache.

See the complete report at file:///opt/atlassian/pipelines/agent/build/build/reports/configuration-cache/cbt8hw9mzxf8uio1l16moak1r/7jy29qovujq3ew8dp737spgf4/configuration-cache-report.html

FAILURE: Build failed with an exception.

* What went wrong:
Configuration cache state could not be cached: field `compileTimeDependencies` of task `:$RAY_KEY_ALIASlibrary:dataBindingMergeDependencyArtifactsDebug` of type `com.android.build.gradle.internal.tasks.databinding.DataBindingMergeDependencyArtifactsTask`: error writing value of type 'org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$ConfigurationFileCollection'
> Could not resolve all files for configuration ':$RAY_KEY_ALIASlibrary:debugCompileClasspath'.
> Could not find com.truizlop.sectionedrecyclerview:library:1.2.0.
Required by:
project :$RAY_KEY_ALIASlibrary
> Could not find com.google.android:flexbox:0.3.2.
Required by:
project :$RAY_KEY_ALIASlibrary
> Could not find io.github.luizgrp.sectionedrecyclerviewadapter:sectionedrecyclerviewadapter:1.0.5.
Required by:
project :$RAY_KEY_ALIASlibrary
> Could not find com.applandeo:material-calendar-view:1.4.0.
Required by:
project :$RAY_KEY_ALIASlibrary
> Could not find com.pierfrancescosoffritti.androidyoutubeplayer:core:10.0.5.
Required by:
project :$RAY_KEY_ALIASlibrary

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/8.0.2/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 12s
Configuration cache entry discarded due to serialization error.
Skipping cache upload for failed step
Searching for files matching artifact pattern app/build/outputs/**

Searching for test report files in directories named [test-results, failsafe-reports, test-reports, TestResults, surefire-reports] down to a depth of 4
Finished scanning for test reports. Found 0 test report files.
Merged test suites, total number tests is 0, with 0 failures and 0 errors.?
```


Answers:
author: Mohamad Dakroub
body: It seems it was "**auto**" resolved -_-


Tags: bitbucket-cloud

cloud