Assigned
Status Update
No update yet.
Comments
da...@hgv.it
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
de...@databricks.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.
fr...@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"
fr...@google.com
Experiencing the same issues, please see my other report for any useful logs:
https://issuetracker.google.com/issues/235673375
de...@databricks.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
vv...@slb.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
Background:
The Batch API for GCS:
1. It supports up to 100 requests in a single request.
2. It can be used for metadata operations and deletes.
3. Cloud Storage does not support batch operations for uploading or downloading.
4. Operations within the batch request are billed separately.
Why is this important?
Instead of sending 100 separate HTTP requests and incurring overhead, a user can send a collection of up to 100 operations in a single HTTP request. GCS handles each operation separately and reduces the HTTP overhead that can exist per request.
Existing Requests:
1.
2.