Support deleteObjects API [162653700]

Assigned

Feature Request

More Info Required

adexe s nau

Status Update

No update yet.

Description

ka...@gmail.com

created issue #1

Aug 3, 2020 05:00PM

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:

Use other S3 client such as aws-sdk-js or minio-js with GCS. The DeleteObjects API does not seems to be supported.

How this might work:

https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjects.html

If applicable, reasons why alternative solutions are not sufficient:

As specified here:

This operation enables you to delete multiple objects from a bucket using a single HTTP request. If you know the object keys that you want to delete, then this operation provides a suitable alternative to sending individual delete requests, reducing per-request overhead.

Other information (workarounds you have tried, documentation consulted, etc): https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjects.html

Comments

gs...@google.com <gs...@google.com> #2Aug 3, 2020 05:37PM

Assigned to gs...@google.com.

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

ka...@gmail.com <ka...@gmail.com> #3Aug 4, 2020 06:06AM

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.

gs...@google.com <gs...@google.com> #4Aug 4, 2020 07:09PM

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"

ka...@gmail.com <ka...@gmail.com> #5Aug 5, 2020 06:12AM

Experiencing the same issues, please see my other report for any useful logs:

https://issuetracker.google.com/issues/235673375

gs...@google.com <gs...@google.com> #6Aug 5, 2020 04:55PM

Reassigned to gc...@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

pa...@blablacar.com <pa...@blablacar.com> #7Dec 1, 2021 07:53PM

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

gu...@gmail.com <gu...@gmail.com> #8Dec 10, 2021 08:33PM

I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨

kh...@google.com <kh...@google.com> #9
Restricted+
Mar 20, 2023 06:02PM

Comment has been deleted.

dh...@hsbc.com <dh...@hsbc.com> #10Apr 18, 2023 09:44PM

As an interim update on this issue: we've been already working on the fix that should be available by Android 13 release. The fix requires thorough testing, I'll keep this bug updated as soon as we have more to share. Thanks!

zh...@workday.com <zh...@workday.com> #11May 4, 2023 11:30PM

@comment#9 The Play Store will eventually require targeting API 33, then 34, etc, so accepting this regression in a customer release would be a time ticking bomb for Wear OS apps.

Thank you for the update @comment#10

ra...@gmail.com <ra...@gmail.com> #12Mar 21, 2024 12:05PM

Hey @

comment#10

, do you have any news to share?

Android 13 is out today and we still have no patch unlike what you said a month ago

do...@sap.com <do...@sap.com> #13May 22, 2024 04:30PM

I have no words for this. Android 13 is labeled "stable" but the Wearable API just doesn't work. Can't this issue be given higher priority? If you want to push WearOS you need to make sure it works normally.

dh...@hsbc.com <dh...@hsbc.com> #14Feb 13, 2025 04:36PM

This issues has been already given high priority (updated external priority on this bug to reflect internal status). The fix is on the way and going through the final rounds of testing, so the roll out is slated to next couple of weeks.

To reiterate what have been mentioned earlier on this bug: this issue affects only apps targeting Android 13, so the apps won't break unless you bump targetSDK version to 33. In case if you want to start working on app compatibility for Android 13 behaviour changes, you could use Compatibility framework to toggle on/off the changes individually for isolated testing.