Assigned
Status Update
No update yet.
Comments
al...@gmail.com
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
le...@settle.eu
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.
mj...@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"
co...@gmail.com
Experiencing the same issues, please see my other report for any useful logs:
https://issuetracker.google.com/issues/235673375
co...@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
as...@appdat.jsc.nasa.gov
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
Add serviceusage.services.use' permission to the 'Logging/Logs Viewer' role
******** Feature Request *******
`gcloud logging read` fails without the 'serviceusage.services.use' permission.
The IAM role 'Logging/Logs Viewer' does not currently contain the 'serviceusage.services.use' permission. The 'Permissions and roles' documentation page [1] does not list 'serviceusage.services.use' as being included in this role nor does it specify that it is needed when using logging logs in Cloud SDK [2].
The Logs Viewer role by itself will allow the user to view logs in Stackdriver via the Cloud Console, but not via 'gcloud logging', which returns an error message:
ERROR: (gcloud.logging.logs.list) User [USER-NAME] does not have permission to access project [PROJECT-ID] (or it may not exist): Caller does not have required permission to use project unknown. Grant the caller the Owner or Editor role, or a custom role with the serviceusage.services.use permission, by visiting
Reference:
[1]
[2]