Bitrise Build Issue Report template
Description of the issue
Bitrise build is failing here
▸ * What went wrong:
▸ Execution failed for task ‘:core:dataBindingMergeDependencyArtifactsProdDebug’.
▸ > Could not resolve all files for configuration ‘:core:prodDebugCompileClasspath’.
▸ > Could not find jp.wasabeef:glide-transformations:4.2.0.
Environment:
Issue is happening in prod at fastlane
If on Bitrise.io: which stack? If not on Bitrise.io: on what operating system? (Plus any other information you can share)
Which build Step causes the issue and which version of the step?
E.g.: Git Clone v3.6.0
Build log
[04:35:29]: ▸ -----------
[04:35:29]: ▸ * What went wrong:
[04:35:29]: ▸ Execution failed for task ‘:core:dataBindingMergeDependencyArtifactsProdDebug’.
[04:35:29]: ▸ > Could not resolve all files for configuration ‘:core:prodDebugCompileClasspath’.
[04:35:29]: ▸ > Could not find jp.wasabeef:glide-transformations:4.2.0.
[04:35:29]: ▸ Required by:
[04:35:29]: ▸ project :core
[04:35:29]: ▸ * Try:
[04:35:29]: ▸ > Run with --stacktrace option to get the stack trace.
[04:35:29]: ▸ > Run with --info or --debug option to get more log output.
[04:35:29]: ▸ > Run with --scan to get full insights.
[04:35:29]: ▸ ==============================================================================
[04:35:29]: ▸ 2: Task failed with an exception.
[04:35:29]: ▸ -----------
[04:35:29]: ▸ * What went wrong:
[04:35:29]: ▸ Execution failed for task ‘:app-mudah:checkProdDebugDuplicateClasses’.
[04:35:29]: ▸ > Could not resolve all files for configuration ‘:app-mudah:prodDebugRuntimeClasspath’.
[04:35:29]: ▸ > Could not find jp.wasabeef:glide-transformations:4.2.0.
[04:35:29]: ▸ Required by:
[04:35:29]: ▸ project :app-mudah > project :core
[04:35:29]: ▸ * Try:
[04:35:29]: ▸ > Run with --stacktrace option to get the stack trace.
[04:35:29]: ▸ > Run with --info or --debug option to get more log output.
[04:35:29]: ▸ > Run with --scan to get full insights.
[04:35:29]: ▸ ==============================================================================
[04:35:29]: ▸ * Get more help at https://help.gradle.org
[04:35:29]: ▸ Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
[04:35:29]: ▸ You can use ‘–warning-mode all’ to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
[04:35:29]: ▸ See Command-Line Interface
[04:35:29]: ▸ BUILD FAILED in 1m 11s
[04:35:29]: ▸ 359 actionable tasks: 343 executed, 16 up-to-date
±------------------------------------+
| Lane Context |
±------------------±----------------+
| DEFAULT_PLATFORM | android |
| PLATFORM_NAME | android |
| LANE_NAME | android staging |
| GRADLE_BUILD_TYPE | Debug |
| GRADLE_FLAVOR | prod |
±------------------±----------------+
[04:35:29]: Called from Fastfile at line 39
[04:35:29]: [04:35:29]: 37: end [04:35:29]: 38: [04:35:29]: => 39: gradle(task: "clean assemble", [04:35:29]: 40: flavor: staging_name, [04:35:29]: 41: build_type: build_type, [04:35:29]:
[04:35:29]: Exit status of command ‘/bitrise/src/gradlew clean assembleprodDebug -p . -Pandroid.injected.signing.store.file=/bitrise/src/debug.keystore -Pandroid.injected.signing.store.password=android -Pandroid.injected.signing.key.alias=androiddebugkey -Pandroid.injected.signing.key.password=android’ was 1 instead of 0.
Configuration on demand is an incubating feature.
