IssueTracker

Can you please add the following to your Module/build.gradle file and run ./gradlew :Module:minifyNetCleanReleaseWithR8 > output.txt, and upload output.txt?

gradle.taskGraph.whenReady {
    this.allTasks.forEach { t ->
        println("Task name = " + t.name + ": ")
        println(t.outputs.files.joinToString())
        println(" ---- done with outputs for " + t.name)
    }
}

Also, can you please share full stacktrace (./gradlew :Module:minifyNetCleanReleaseWithR8 --stacktrace)?

From logs in #3, I can see:

:Module:mergeNetCleanReleaseJavaResource SKIPPED
:NeoTheme:bundleLibRuntimeToJarNetCleanRelease SKIPPED
:BaseModule:bundleLibRuntimeToJarNetCleanRelease SKIPPED
:Module:minifyNetCleanReleaseWithR8 SKIPPED

i.e. mergeNetCleanReleaseJavaResource runs before R8, so dependency info seems fine.

However, from logs:

ERROR: /home/andrew/StudioProjects/Projects/Module/build/intermediates/merged_java_res/netCleanRelease/base.jar: R8: com.android.tools.r8.ResourceException: com.android.tools.r8.internal.Sb: I/O exception while reading '/home/andrew/StudioProjects/MoPoClient_Android2/MoPoClub/build/intermediates/merged_java_res/netCleanRelease/base.jar': /home/andrew/StudioProjects/Project/Module/build/intermediates/merged_java_res/netCleanRelease/base.jar

which seems odd. I cannot find any other reference to MoPoClient_Android2 in the logs. Do you have some additional info on this?

I succeeded to replicate error for template project: netCleanDebug verssion works, but netCleanRelease fails with base.jar not found

Thanks for sharing the repro. The issue is in the build script that triggers eager task creation, which breaks AGP task configuration. Please use:

tasks.configureEach {
     if(name.startsWith("connectedNet")) {
        enabled = false
    }
}

instead of tasks.whenTaskAdded (see Gradle docs for more info). After this modification, R8 will fail with missing classes, so please follow instructions at https://developer.android.com/build/releases/past-releases/agp-7-0-0-release-notes#r8-missing-class-warning to fix that.

Sidenote: I'd advise against disabling tasks in this way. If you'd like to disable instrumented tests, see https://github.com/android/gradle-recipes/blob/0db8094e5a1a9661f61958db85380320157f5050/Groovy/disableAndroidTest/app/build.gradle#L15.

Saved my day, faced with following issue after migration to AGP 8.1.0. Can confirm tasks.configureEach {} fix the problem

This fixed my compilation crash as well - however, configureEach does not work the same. I want to attach the lintDevDebug task to my sonar task, and was doing it like so:

project.tasks.whenTaskAdded {
   if (name == "lintDevDebug") {
      project.rootProjects.tasks.findByName("sonar")?.let { sonarTask ->
          sonarTask.dependsOn(this)
      }
   }
}

Replacing whenTaskAdded with configureTask, I never see a task with the name of lintDevDebug - I never see any of the tasks added by the android plugin.

If we can't use whenTaskAdded, how are we supposed to hook into the AGP provided tasks now?

It might have been nice if this breaking change with whenTaskAdded was mentioned in the release notes when 8.1 became stable. The lint warning/intention action is helpful, but not severe enough since it is definitely going to break minified builds.

Re #8: configureEach is triggered differently from whenTaskAdded, only when there is a direct request to execute it or another task depends on it. In general, we discourage setting task dependencies explicitly; instead these should be modeled through AGP APIs (https://developer.android.com/reference/tools/gradle-api). In case your use-case is unsupported, please file a bug and we can consider adding a new feature.

Coming back to your snippet, this should work:

project.tasks.configureEach {
   if (name == "sonar") {
      it.dependsOn("lintDevDebug")
   }
}

Re #9: This Gradle API is pretty much incompatible with lazy task configuration (https://docs.gradle.org/current/userguide/lazy_configuration.html) that's been a standard for a while. Gradle should start warning about these usages and start offering replacement APIs. You can file a bug on their issue tracker - https://github.com/gradle/gradle/issues/.

See previous comments #6 and #10 on how to fix this issues, thanks.

It seems like the JAR is there at the end of the previous task. R8 checks that the jar is there (see screenshot)

Then the logs show

2023-08-26T09:40:31.870-0400 [DEBUG] [org.gradle.internal.vfs.impl.AbstractVirtualFileSystem] Invalidating VFS paths: [/build/projects/app/tfa/outputs/mapping/defaultRelease/mapping.txt, /build/projects/app/tfa/outputs/mapping/defaultRelease/missing_rules.txt, /build/projects/app/tfa/intermediates/merged_art_profile/defaultRelease/baseline-prof.txt, /build/projects/app/tfa/intermediates/dex/defaultRelease/minifyDefaultReleaseWithR8, /build/projects/app/tfa/intermediates/merged_java_res/defaultRelease/base.jar, /build/projects/app/tfa/outputs/mapping/defaultRelease/configuration.txt, /build/projects/app/tfa/outputs/mapping/defaultRelease/seeds.txt, /build/projects/app/tfa/outputs/mapping/defaultRelease/usage.txt]

Then the minify task fails. It seems like no other task is running at the same time and I can only assume that r8 is removing the JAR itself? This seems like a bug?

Also running into the issue here, not using whenTaskAdded.
I managed to fix it since I found the following config in our module to edit test config:

tasks.matching { it instanceof Test }.all { // Show more test execution information
    testLogging.events = ["failed", "passed", "skipped"]
    testLogging.exceptionFormat "full"
}

Instead of the .all, we need to use .configureEach here!

FYI, in our case the culprit was a 3rd-party plugin "ru.cian.huawei-publish" whose version we used (1.3.5) was not compatible with AGP 8+. In order to find it, we had to comment out each plugin one by one until gradle assembleRelease was succeeding. Once we upgraded the plugin to an AGP 8+-supporting version (1.4.0), the problem went away.

I ran into this upgrading from gradle 8.0.2 to 8.2.2, to match upgrading from Android Studio Flamingo to Hedgehog.

I made all the changes directed in the Gradle Task Configuration Avoidance page as suggested by #19, but the problem was still there.

Using the approach listed in #24, I found that the culprit for me was this snippet in my :app build.gradle file:

ant.importBuild("${<location-of-ant-project>}/build.xml") { antTargetName ->
    '<prefix-I-used>-' + antTargetName
}

For me this was not currently in use, so I've just commented it out, but it seems to me that perhaps it's a gradle (packaging?) bug with the implementation of AntBuilder org.gradle.api.Project.getAnt() that's shipping with Android Studio?

#29 and #30 if you are not using any of the "eager apis" outlined here (https://docs.gradle.org/current/userguide/task_configuration_avoidance.html#sec:old_vs_new_configuration_api_overview) and still getting the error, can you please share a reproudcing project or a sample build file for the module where the error is happening?

Please include a list of third party plugins you are depending on too.