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

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

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

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

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.

Also, I'm seeing this message in the Logcat:

"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"

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

Experiencing the same issues, please see my other report for any useful logs:

https://issuetracker.google.com/issues/235673375

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

+1, can confirm it doesn't work on Android 13:=

2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver }
2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Access blocked: ComponentInfo{xxx/xxx.WatchMessageReceiver}
2022-07-15 11:26:15.023   589-5347  ActivityManager         pid-589                              W  Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver } U=0: not found

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

Marked as fixed.

Note that I've been able to make it work by:

Adding <action android:name="com.google.android.gms.wearable.BIND_LISTENER" /> in the intent filter
Removing <data android:scheme="wear" android:host="*" />

But I feel like this is not something we should do

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

I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨