Assigned
Status Update
No update yet.
Comments
pt...@google.com
ma...@google.com
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
er...@gmail.com
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.
mp...@google.com
js...@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"
"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"
mp...@google.com
Experiencing the same issues, please see my other report for any useful logs:
https://issuetracker.google.com/issues/235673375
bh...@gmail.com
+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
[Deleted User] <[Deleted User]>
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
ol...@klp.no
I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨
mp...@google.com
me...@google.com
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.
Description
This case initially came from a stackoverflow case [1].
The Project owner granted him the Compute engine Admin role.
The user did not receive an invitation email.
And when he tries to access it through the link [2], it will not work.
I've tested it on my end, and I experience the same results. The user did not receive an invitation email. The only time when the user received an invitation email is when the "Project Owner" role was assigned.
[1]
[2]
Reproduction steps:
1 - Visit the Cloud IAM section of the console
2 - Grant any role to a user (any role except "Project Owner")
3 - The user will not receive an invitation email.