Assigned
Status Update
Comments
sa...@sainsburys.co.uk <sa...@sainsburys.co.uk> #2
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
jo...@google.com <jo...@google.com>
gl...@mylighthouse.com <gl...@mylighthouse.com> #3
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.
al...@cloudpilots.com <al...@cloudpilots.com> #4
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"
de...@simpleclub.com <de...@simpleclub.com> #5
Experiencing the same issues, please see my other report for any useful logs:
https://issuetracker.google.com/issues/235673375
br...@groupecanam.com <br...@groupecanam.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
Description
Customer is interested in the addition of IAM resources into the IAM Conditions.
Problem you have encountered:
Currently there's no resource type supported to control the IAM permissions through conditions
What you expected to happen:
Find the IAM resources available to control the access to IAM for a user account based on the condition
-Go to the IAM page
-From the list of members, locate the desired member and click the edit button.
-From the Edit permissions panel, locate the desired role to configure a condition for.
-Then under Condition, click Add condition.
-In the condition builder look for the IAM resources to create a condition to allows a user to apply changes when the condition is met, for example:
Other information (workarounds you have tried, documentation consulted, etc):https://cloud.google.com/iam/docs/configuring-resource-based-access
https://cloud.google.com/iam/docs/conditions-resource-attributes
[1]
[2]