Status Update
Comments
ly...@gmail.com <ly...@gmail.com> #2
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
xo...@google.com <xo...@google.com>
je...@google.com <je...@google.com>
am...@google.com <am...@google.com> #3
am...@google.com <am...@google.com> #4
"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"
ly...@gmail.com <ly...@gmail.com> #5
je...@google.com <je...@google.com> #6
+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
cm...@google.com <cm...@google.com>
am...@google.com <am...@google.com> #7
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
cm...@google.com <cm...@google.com> #8
I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨
sp...@google.com <sp...@google.com> #9
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.
xa...@google.com <xa...@google.com> #10
As an interim update on this issue: we've been already working on the fix that should be available by Android 13 release. The fix requires thorough testing, I'll keep this bug updated as soon as we have more to share. Thanks!
cm...@google.com <cm...@google.com> #11
@
Thank you for the update @
ry...@gmail.com <ry...@gmail.com> #12
Android 13 is out today and we still have no patch unlike what you said a month ago
Description
DESCRIBE THE ISSUE IN DETAIL: Assume we have one module A, that declares permission with manifest placeholder:
Also we have another module B that have dependency on module A. This module has some unit tests and enabled
android.testOptions.unitTests.includeAndroidResources = true
inbuild.gradle
. To run unit tests I need to declare manifest placeholder for test variants in module B inbuild.gradle
:When I'm trying to run unit tests in module B I'm getting the error:
But it works correctly with AGP 7.3.1.
Sample project to reproduce:https://github.com/bacecek/sample-checking-assistant-role/tree/broken-test-manifest-placeholders
Studio Build: Android Studio Electric Eel | 2022.1.1. Build #AI-221.6008.13.2211.9477386, built on January 11, 202 Version of Gradle Plugin: 7.4.0 Version of Gradle: 7.5.1 Version of Java: Temurin 17.0.5 OS: macOS 13.1