Protocol is always s3-multipart for remote file uploads with the AwsS3 uploader even with shouldUseMultipart set to false

[StrixOSG]

Initial checklist

• [X] I understand this is a bug report and questions should be posted in the Community Forum
• [X] I searched issues and couldn’t find anything (or linked relevant results below)

Link to runnable example

No response

Steps to reproduce

Choose a remote provider such as Google Drive with AwsS3 as the uploader and uploading files will always be 's3-multipart' even with shouldUseMultipart set to false.

Expected behavior

In previous versions as we recently upgraded from v3 to v4 of Uppy it used 'multipart' and not 's3-multipart' for uploading remote files. I would expect this to still be the case or that you can choose with either passing in the protocol, or with shouldUseMultipart being set to false. This is a problem as we generate the pre-signed urls beforehand to upload to and does not fit nicely in our flow to have to switch to 's3-multipart'.

Actual behavior

When AwsS3 is the uploader, uploading files from remote sources like Google Drive will always be 's3-multipart' instead of 'multipart' even with shouldUseMultipart set to false.

[shabanbx]

@StrixOSG did you find any solution?

[StrixOSG]

@StrixOSG did you find any solution?

Nothing yet. I tried intercepting the request as a workaround and changing the protocol to 'multipart' but it appears to be more involved then that as it now says "no destination specified"

[StrixOSG]

@mifi any thoughts?