Fixed

Bug

Status Update

No update yet.

Description

au...@google.com

created issue #1

Oct 10, 2022 07:31PM

DESCRIBE THE ISSUE IN DETAIL: Gradle 8.0-milestone-2 causes exception in AGP

STEPS TO REPRODUCE:

Run an AGP project while using Gradle 8.0-milestone-2

Expected:

No exceptions

Actual:

Exception

Unable to decide if config caching is enabled	
java.lang.NoSuchMethodError: 'org.gradle.internal.buildoption.BuildOption$Value org.gradle.api.internal.StartParameterInternal.getConfigurationCache()'	
        at com.android.build.gradle.internal.StartParameterUtils.isConfigurationCache(StartParameterUtils.kt:30)	
        at com.android.build.gradle.internal.profile.AnalyticsResourceManager.recordGlobalProperties(AnalyticsResourceManager.kt:301)

https://ge.androidx.dev/s/m4okntwz2h4oo/console-log?anchor=445&page=1

AGP is using internal API that just got refactored in https://github.com/gradle/gradle/commit/8b7dda9a763379c031712ceabcf9ec04cbf87a5e

Note, this does not fail the build, but it does print a giant exception to the log.

Comments

ga...@google.com <ga...@google.com> Oct 11, 2022 06:28AM

Assigned to bi...@google.com.

bi...@google.com <bi...@google.com> Oct 11, 2022 04:34PM

Accepted by bi...@google.com.

bi...@google.com <bi...@google.com> #2Oct 11, 2022 08:06PM

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

au...@google.com <au...@google.com> #3Oct 11, 2022 08:07PM

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.

au...@google.com <au...@google.com> #4Oct 28, 2022 08:59PM

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"

bi...@google.com <bi...@google.com> #5Oct 28, 2022 10:04PM

Marked as fixed.

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

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

sa...@google.com <sa...@google.com> #6Nov 2, 2022 05:32PM

+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

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

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

ph...@gmail.com <ph...@gmail.com> #8Nov 3, 2022 06:26PM

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

pa...@gmail.com <pa...@gmail.com> #9Jan 4, 2023 04:01PM

If you're not targeting API 33 you're not affected by the bug. So it's a big bug, and yes we of course expected more from Google, but you can always target the api level later when it's fixed.

But I agree this is kind of desperating that more than 1.5 month after the first report nothing has changed.