Assigned
Status Update
No update yet.
Comments
di...@google.com
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
Z_...@bespinglobal.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.
de...@nagra.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"
ia...@voltrondata.com
Experiencing the same issues, please see my other report for any useful logs:
https://issuetracker.google.com/issues/235673375
dh...@google.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
ma...@netcracker.com
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
Description
We can use labels when we create a resource in GCP but we can’t force the usage of this labels to resources as they create them, and deny the creation if the label is not present because the adding/updating labels labels on a GCP resources is available to be chosen but not an obligatory requirement. Customer is requesting for a feature request that helps to force the usage if a label while creating a specific GCP resource (ex: GCE Instance, GCS Bucket).
Use case:
Customer's Service teams are permitted to deploy their own resources within the cloud to facilitate ownership and rapid deployment. So, deployments don't go through a central team that could attach labels. By forcing teams to label their deployed resources correctly, we can then use the labels for various important tracking purposes.
Customer's ideal enforcement policy for the above use case is provided below:
"In project 'MyDevProject', you can create resource X only when you include the label that has a key named Owner with any string value."
"In project 'MyProductionProject', you can create resource X only when you include two labels, with the keys Owner and Service."