Uniform access is trying to set ACLs for Google buckets

[simesy]

Describe the bug
When I connect to a Google Bucket which doesn't has Uniform Access, and I set Cyberduck Default ACL to None, Cyberduck is uploading the file but ends with the following message:

Invalid argument. Cannot insert legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access. Please contact your web hosting service provider for assistance.

To Reproduce
Docs mentioned below are https://docs.duck.sh/protocols/googlecloudstorage/

1. Create a google cloud bucket
2. Set Access control: Uniform
3. Create an Amazon S3 bookmark in Cyberduck (per use s3 compatible, not Google Storage)
4. Set server to storage.googleapis.com (again per docs)
5. In Cyberduck settings, Click the Google tab, Set Default ACL: None.
6. Connect to the S3 and try to upload a file - you should see file uploading.
7. Note the error after the file has finished uploading.
   Screenshots

Desktop (please complete the following information):

• MacOS Silicon
• Version 9.1.2 (42722)

Log Files
Attached with some redacted

acl-error.log

Commentary

It reads like this is the same issue as #11766, which ended with you adding an option in the Settings to set Default ACL = None. I have tried various options but I think am sure that None is correct. I assume this used to work at some point and Assuming that others are using this option with Cyberduck. I have waited a few versions before creating this issue, it seems to have been around for a while.

[dkocher]

The fix for #11766 was implemented for the Google Storage connect option. This is also supported for S3 as described in #13386 but using the S3 APIs not supported by the Google Storage interoperability layer for S3 as indicated in the log file provided.

The ownershipControls parameter is ignored

2025-01-26 13:01:42,796 [5QyOAgW9-transfer-1] INFO  ch.cyberduck.transcript.request - GET /?ownershipControls= HTTP/1.1

What is your motivation to use S3 to connect instead of the native Google Storage APIs that are supported?

[simesy]

My interpretation of the documentation was wrong I suppose. I want to connect natively but it reads like I am supposed to use the S3 type, while the Google storage type I assumed must be for Drive and other storage types.

I'll have a fresh attempt using native connector, thanks.