Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Assemble failing on Kotlin multiplatform project during `generateSentryBundleId`

Open
  • Is something wrong?
#1,089 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
android, kotlin
Domain
build-system

Research direction

Start with the Gradle validation output for :composeApp:generateSentryBundleIdFullRelease and the related resource-generation tasks named in the report. Trace how the Sentry Android Gradle Plugin configures that task and verify its relationship with the Compose resource tasks. Done means the reported implicit-dependency errors are resolved and the assemble tasks complete successfully.

Written by the indexing model from the issue text.

Description

Android Bug Errors
Gradle Version

9.0.0

AGP Version

8.13.0

Code Minifier/Optimizer

R8

Version

6.1.0

Sentry SDK Version

0.24.0 (multiplatform)

Steps to Reproduce

We were already using the sentry kotlin multiplatform library, and we just added the Sentry Android Gradle Plugin to automatically upload proguard mappings. But it's failling to run assemble gradle tasks.

Here's pull-request for adding the gradle plugin: https://github.com/ooni/probe-multiplatform/pull/1175

Expected Result

assemble tasks run fine

Actual Result

Gradle fails with:

[8](https://github.com/ooni/probe-multiplatform/actions/runs/22577882536/job/65401765244?pr=1175#step:4:139)
FAILURE: Build failed with an exception.

* What went wrong:
Some problems were found with the configuration of task ':composeApp:generateSentryBundleIdFullRelease' (type 'GenerateBundleIdTask').
  - Gradle detected a problem with the following location: '/home/runner/work/probe-multiplatform/probe-multiplatform/composeApp/build/generated/compose/resourceGenerator/kotlin/androidMainResourceAccessors'.
    
    Reason: Task ':composeApp:generateSentryBundleIdFullRelease' uses this output of task ':composeApp:generateResourceAccessorsForAndroidMain' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
    
    Possible solutions:
      1. Declare task ':composeApp:generateResourceAccessorsForAndroidMain' as an input of ':composeApp:generateSentryBundleIdFullRelease'.
      2. Declare an explicit dependency on ':composeApp:generateResourceAccessorsForAndroidMain' from ':composeApp:generateSentryBundleIdFullRelease' using Task#dependsOn.
      3. Declare an explicit dependency on ':composeApp:generateResourceAccessorsForAndroidMain' from ':composeApp:generateSentryBundleIdFullRelease' using Task#mustRunAfter.
    

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

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

For more on this, please refer to https://docs.gradle.org/9.0.0/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
44 actionable tasks: 44 executed
    For more information, please refer to https://docs.gradle.org/9.0.0/userguide/validation_problems.html#implicit_dependency in the Gradle documentation.
  - Gradle detected a problem with the following location: '/home/runner/work/probe-multiplatform/probe-multiplatform/composeApp/build/generated/compose/resourceGenerator/kotlin/androidMainResourceCollectors'.
    
    Reason: Task ':composeApp:generateSentryBundleIdFullRelease' uses this output of task ':composeApp:generateActualResourceCollectorsForAndroidMain' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
    
    Possible solutions:
      1. Declare task ':composeApp:generateActualResourceCollectorsForAndroidMain' as an input of ':composeApp:generateSentryBundleIdFullRelease'.
      2. Declare an explicit dependency on ':composeApp:generateActualResourceCollectorsForAndroidMain' from ':composeApp:generateSentryBundleIdFullRelease' using Task#dependsOn.
      3. Declare an explicit dependency on ':composeApp:generateActualResourceCollectorsForAndroidMain' from ':composeApp:generateSentryBundleIdFullRelease' using Task#mustRunAfter.
    
    For more information, please refer to https://docs.gradle.org/9.0.0/userguide/validation_problems.html#implicit_dependency in the Gradle documentation.

* Try:
> Declare task ':composeApp:generateResourceAccessorsForAndroidMain' as an input of ':composeApp:generateSentryBundleIdFullRelease'
> Declare an explicit dependency on ':composeApp:generateResourceAccessorsForAndroidMain' from ':composeApp:generateSentryBundleIdFullRelease' using Task#dependsOn
> Declare an explicit dependency on ':composeApp:generateResourceAccessorsForAndroidMain' from ':composeApp:generateSentryBundleIdFullRelease' using Task#mustRunAfter
> Declare task ':composeApp:generateActualResourceCollectorsForAndroidMain' as an input of ':composeApp:generateSentryBundleIdFullRelease'
> Declare an explicit dependency on ':composeApp:generateActualResourceCollectorsForAndroidMain' from ':composeApp:generateSentryBundleIdFullRelease' using Task#dependsOn
> Declare an explicit dependency on ':composeApp:generateActualResourceCollectorsForAndroidMain' from ':composeApp:generateSentryBundleIdFullRelease' using Task#mustRunAfter
Dominant language
Kotlin
Stars
184
Forks
41
Avg merge
1d 23h
Merged PRs (30d)
19

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-android-gradle-plugin

All issues in getsentry/sentry-android-gradle-plugin

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.