Hi, I just tested locally and I do get the complete file path. Are you on latest versions of everything?

Yes, npm outdated shows that everything is up-to-date.

(This is using DigitalOcean Spaces as S3 storage - though this has worked fine for us with previous versions of Uppy).

It works for me for S3 and we don't officially support or test against DigitalOcean Spaces. If you can reproduce on S3 that would be great. Otherwise you may have to contribute yourself to fix it.

I have the same issue with AWS S3 where it returns only the base bucket URL.

1

I also use AWS S3 and I can see the uppy uploaded file in S3 cache folder.
However, Im also only not getting the base bucket URL in uploadURL key.

not using Companion but Shrine plugin

"@uppy/aws-s3": "^4.0.3",
"@uppy/core": "^4.1.2",
"@uppy/dashboard": "^4.0.3",
"@uppy/locales": "^4.0.3",

gem "shrine", "~> 3.6.0"

this is a complete example response (notice the weird "": "" key in the reponse body key which might be a clue):

{
"source": "Dashboard",
"id": "sample/image/jpeg-2v-2v-1e-image/jpeg-91516-1671405542014",
"name": "sample_image.jpeg",
"extension": "jpeg",
"meta": {
"relativePath": null,
"name": "sample_image.jpeg",
"type": "image/jpeg"
},
"type": "image/jpeg",
"data": {
"lastModified": 1724512075822,
"lastModifiedDate": "2024-08-24T15:07:55.822Z",
"name": "sample_image.jpeg"
},
"progress": {
"uploadStarted": 1724512075828,
"uploadComplete": true,
"percentage": 100,
"bytesUploaded": 64790,
"bytesTotal": 64790
},
"size": 64790,
"isGhost": false,
"isRemote": false,
"preview": "blob:http://localhost:3000/727c9392-9254-4115-84e9-65d37a09ee56",
"response": {
"body": {
"location": "https://devtech-edukaierp-dev.s3.amazonaws.com/",
"": ""
},
"status": 200,
"uploadURL": "https://devtech-edukaierp-dev.s3.amazonaws.com/"
},
"uploadURL": "https://devtech-edukaierp-dev.s3.amazonaws.com/",
"isPaused": false
}

When using @uppy/aws-s3 and doing non multi-part uploads, the nonMultipartUpload method is used from HTTPCommunicationQueue.

Seems that every other uploading method in HTTPCommunicationQueue is doing

const { uploadId, key } = await this.getUploadId(file, signal)

, and then adding the key to the returned result.

No such luck with the nonMultipartUpload method.

The multipart upload (shouldUseMultipart = true) returns the full URL but the nonMultipartUpload doesn't. It's just a bucket URL. :(

1 that this is broken for:

• aws s3
• non-multipart upload