New "unknown enum constant" from javac on AGP 7.4.0-alpha09 [241287611]

Fixed

Bug

Status Update

No update yet.

Description

pi...@gmail.com

created issue #1

Aug 4, 2022 03:18AM

DESCRIBE THE ISSUE IN DETAIL:

I maintain a Gradle plugin that, among other things, depends on:

com.android.tools.build:android-gradle-plugin
com.android.tools:r8
com.android.tools:repository

On AGP 7.4.0-alpha08, my project builds without warnings or errors. When I update it to alpha09, I see the following build failure (due to enabling warnings-as-errors):

> Task :compileJava FAILED
warning: unknown enum constant TaskCategoryLabel.AAR_PACKAGING
  reason: class file for com.android.ide.common.attribution.TaskCategoryLabel not found
error: warnings found and -Werror specified
1 error
1 warning

This enum comes from sdk-commons. I don't explicitly depend on this, and interestingly, none of my code seems to reference it, either. Adding a compileOnly dependency on sdk-commons resolves the error; it appears to me as if AGP transitively depends on sdk-commons, and between alpha08 and alpha09 something in that transitive chain changed from an api dependency to an implementation dependency.

STEPS TO REPRODUCE:

git clone https://github.com/keepsafe/dexcount-gradle-plugin
git checkout agp-7.4.0-alpha09
Comment out line 90 of build.gradle
./gradlew compileJava

ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE

ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)

IMPORTANT: Please read https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

Studio Build: N/A Version of Gradle Plugin: 7.4.0-alpha09 Version of Gradle: 7.5 Version of Java: 11.0.15 (Azul Systems, Inc. 11.0.15+10-LTS) OS: Mac OS X 12.4 aarch64

Comments

pi...@gmail.com <pi...@gmail.com> #2Aug 4, 2022 03:22AM

Will be this fix also part of 4.2 please?

xa...@google.com <xa...@google.com> #3Aug 4, 2022 03:46PM

Assigned to cm...@google.com.

for the "out" bundle issue, this seems indeed an issue. for the second one reported adding "debugUpdateAPKArtifact" to the path, this WAI as there can more more than one transformer and we need to automatically separate them so they do not use the same output folder. for #3, I will look at it but it might be difficult to change it at this time.

cm...@google.com <cm...@google.com> #4Aug 4, 2022 04:14PM

I understand that if there is more transformer is necessary to make every folder different, but there is the main problem, that the final one (last transform) is inside of the intermediate folder. The last transformation should end in the standard location, right? Maybe also with the default name not?

cm...@google.com <cm...@google.com> #5Aug 4, 2022 04:15PM

Hello, this is a P1 S1 issue for a while now, and it's blocking us from upgrading to AGP 4.2 and further. What's the current status? And do you have plans to backport it to 4.2.x?

am...@google.com <am...@google.com> #6Aug 4, 2022 04:39PM

Reassigned to an...@google.com.

no we don't have a plan to backport this. why is this blocking you from upgrading ?

uc...@google.com <uc...@google.com> Aug 8, 2022 07:55AM

Reassigned to an...@google.com.

ga...@google.com <ga...@google.com> Aug 8, 2022 08:06AM

Reassigned to an...@google.com.

an...@google.com <an...@google.com> Aug 23, 2022 11:05AM

Accepted by an...@google.com.

an...@google.com <an...@google.com> Aug 24, 2022 12:54PM

Marked as fixed.

pi...@gmail.com <pi...@gmail.com> #7Aug 26, 2022 04:32PM

We sign apk's and bundles via internal service, and i don't know another way to interact with artifacts; Yesterday i ended up with some ugly workaround: https://github.com/avito-tech/avito-android/pull/1085/files#diff-b898cc20fedebe394439bb37ffb91d3366a1f9a6d359dbdebca79af8a079f911 I'd be glad if you'll point me out how can it be done better.

sa...@google.com <sa...@google.com> #8Nov 3, 2022 01:42PM

I commented on the merge request but to summarize :

you can set your signing tasks output folder to wherever you need to be :

artifacts.use(target.tasks.signedApkTaskProvider(this)).configure { signedDirProperty.set(File("/path/to/where/you/want/your/signed/files")) }

if you don't set it, then we will set a directory automatically.

Issue 241287611

Description

Issue summary

Comments

pi...@gmail.com <pi...@gmail.com> #2Aug 4, 2022 03:22AM

xa...@google.com <xa...@google.com> #3Aug 4, 2022 03:46PM

cm...@google.com <cm...@google.com> #4Aug 4, 2022 04:14PM

cm...@google.com <cm...@google.com> #5Aug 4, 2022 04:15PM

am...@google.com <am...@google.com> #6Aug 4, 2022 04:39PM

uc...@google.com <uc...@google.com> Aug 8, 2022 07:55AM

ga...@google.com <ga...@google.com> Aug 8, 2022 08:06AM

an...@google.com <an...@google.com> Aug 23, 2022 11:05AM

an...@google.com <an...@google.com> Aug 24, 2022 12:54PM

pi...@gmail.com <pi...@gmail.com> #7Aug 26, 2022 04:32PM

sa...@google.com <sa...@google.com> #8Nov 3, 2022 01:42PM

Add comment

Issue metadata