Using @IntDef in a library component doesn't generate annotations.zip in the aar [228751486]

Fixed

Bug

Status Update

No update yet.

Description

ja...@gmail.com

created issue #1

Apr 11, 2022 01:31PM

When creating a library component that uses @IntDef annotations in its public API, I am expecting that the annotations.zip is packaged inside that aar - from here, it states:

If you use annotations in your own library module, the annotations are included as part of the Android Archive (AAR) artifact in XML format in the annotations.zip file. Adding the support-annotations dependency does not introduce a dependency for any downstream users of your library.

However, this doesn't appear to be the case, and the build/intermediates/annotations_typedef_file/debug/typedefs.txt file is empty (I'm assuming this would contain something?) as is the build/intermediates/annotations_zip/debug/ dir.

I'm using AGP 7.0.3 with Gradle version 7.0.2 in Android Studio Bumblebee 2021.1.1. Patch 2.

(NOTE: I re-raised this ticket, as https://issuetracker.google.com/issues/227147440 was likely in too high-level a bucket. Apologies for the dupe.)

Comments

al...@google.com <al...@google.com> #2Apr 11, 2022 01:47PM

Status: New

Will be this fix also part of 4.2 please?

ja...@gmail.com <ja...@gmail.com> #3Apr 11, 2022 01:57PM

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.

em...@google.com <em...@google.com> Apr 11, 2022 03:19PM

Assigned to an...@google.com.

je...@google.com <je...@google.com> Apr 11, 2022 07:39PM

Reassigned to bi...@google.com.

bi...@google.com <bi...@google.com> #4Apr 11, 2022 07:54PM

Accepted by bi...@google.com.

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?

ja...@gmail.com <ja...@gmail.com> #5Apr 11, 2022 10:29PM

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?

bi...@google.com <bi...@google.com> #6Sep 28, 2022 05:49PM

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

bi...@google.com <bi...@google.com> #7Sep 28, 2022 10:44PM

Marked as fixed.

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.

ja...@gmail.com <ja...@gmail.com> #8Sep 29, 2022 08:28AM

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.