Assigned
Status Update
No update yet.
Comments
am...@google.com
ma...@gmail.com
Comment has been deleted.
ed...@joy.co
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.
ha...@silvr.co
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"
en...@ingka.ikea.com
Experiencing the same issues, please see my other report for any useful logs:
https://issuetracker.google.com/issues/235673375
sp...@imandra.ai
+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
This will create a feature request which anybody can view and comment on.
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
I would like to deploy a public cloudfunction gen2 via terraform, but the IAM role
roles/cloudfunctions.invokerdoes not have permissions forrun.routes.invoke. The next role with the necessary permissions would beroles/cloudfunctions.developerwhich has far too many permissions for an unauthenticated user.How this might work:
Add
run.routes.invoketoroles/cloudfunctions.invokerIf applicable, reasons why alternative solutions are not sufficient:
It seems unclean to use the API from another resource to set the IAM permissions.
Other information (workarounds you have tried, documentation consulted, etc):
A functioning workaround is to use the API for cloud run (https://cloud.google.com/run/docs/reference/iam/roles ) and set the role
roles/run.invoker.