Give kotlin gradle syntax in error message for `checkTestedAppObfuscationRelease` [378724144]

Fixed

Bug

Status Update

No update yet.

Description

yo...@gmail.com

created issue #1

Nov 12, 2024 09:51PM

AGP 8.7.2

Use com.android.test plugin to create app tests with GMD.

run :app-tests:my-feature:cpixel2api30ReleaseAndroidTest

Actual

Error gives only groovy gradle syntax I get this error:

> Task :app-tests:my-feature:checkTestedAppObfuscationRelease FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app-tests:my-feature:checkTestedAppObfuscationRelease'.
> Mapping file found in tested application. Code shrinker must also be enabled in test plugin with:
  android {
      buildTypes {
          release {
              minifyEnabled true
          }
      }
  }

Expected

give Kotlin syntax as well.

i.e.

  android {
      buildTypes {
          register("release") {
              isMinifyEnabled = true
          }
      }
  }

Comments

ra...@google.com <ra...@google.com> Nov 13, 2024 11:06PM

Assigned to an...@google.com.

je...@google.com <je...@google.com> Nov 15, 2024 03:53PM

Reassigned to hu...@google.com.

hu...@google.com <hu...@google.com> #2Dec 11, 2024 11:54AM

Marked as fixed.

Caused by: java.lang.IndexOutOfBoundsException: Empty list doesn't contain element at index 0.
        at kotlin.collections.EmptyList.get(Collections.kt:37)
        at kotlin.collections.EmptyList.get(Collections.kt:25)
        at com.android.tools.lint.Main.createLintRequest(Main.java:1747)
        at com.android.tools.lint.Main.run(Main.java:280)
        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
        at com.android.build.gradle.internal.lint.AndroidLintWorkAction.invokeLintMainRunMethod(AndroidLintWorkAction.kt:103)
        at com.android.build.gradle.internal.lint.AndroidLintWorkAction.runLint(AndroidLintWorkAction.kt:90)
        at com.android.build.gradle.internal.lint.AndroidLintWorkAction.execute(AndroidLintWorkAction.kt:64)
        at org.gradle.workers.internal.DefaultWorkerServer.execute(DefaultWorkerServer.java:63)
        at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1.create(NoIsolationWorkerFactory.java:66)
        at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1.create(NoIsolationWorkerFactory.java:62)
        at org.gradle.internal.classloader.ClassLoaderUtils.executeInClassloader(ClassLoaderUtils.java:100)
        at org.gradle.workers.internal.NoIsolationWorkerFactory$1.lambda$execute$0(NoIsolationWorkerFactory.java:62)
        ... 23 more

https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:lint/cli/src/main/java/com/android/tools/lint/Main.java;l=1737-1749;drc=7cd900c1d6ace2584979fae35e3abda3cda47343

            // Set up lint project dependencies based on the model
            boolean isReporting = argumentState.mode == LintDriver.DriverMode.MERGE;
            List<LintModelModuleProject> roots =
                    LintModelModuleProject.resolveDependencies(projects, isReporting);

            lintRequest = new LintRequest(client, Collections.emptyList());
            lintRequest.setProjects(roots);

            if (isReporting) {
                EnumSet<Platform> platforms =
                        roots.get(0).isAndroidProject() ? Platform.ANDROID_SET : Platform.JDK_SET;
                lintRequest.setPlatform(platforms);
            }

It seems like that roots is empty (for lintReportJvm).

an...@google.com <an...@google.com> #3Dec 16, 2024 07:32PM

Execution failed for task ':lintReportJvm'

OP, are you applying the lint plugin to the root Gradle project? I'm guessing that's the problem here... assuming you only want to apply the lint plugin to modules with source code, etc.

da...@gmail.com <da...@gmail.com> #4Dec 29, 2024 04:21PM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Meerkat | 2024.3.1 Canary 1
Android Gradle Plugin 8.9.0-alpha01

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!