Uppy url upload fail

Uppy
1

Hi, I am trying to set up Uppy url upload in my application, however, it keep looping url/get request and websocket communication from Uppy companion internally, so the process never finished. The message returned from websocket connected to the companion shows success message.

Is there anything important to set up on client/server side that is a must in order to enable Uppy url upload? I am using Uppy in React, but not the latest Uppy React package.

Here is the version I am using:

"@uppy/aws-s3": "^3.6.0",
"@uppy/box": "^2.2.0",
"@uppy/compressor": "^1.0.5",
"@uppy/core": "^3.8.0",
"@uppy/dashboard": "^3.7.1",
"@uppy/drag-drop": "^3.0.3",
"@uppy/dropbox": "^3.2.0",
"@uppy/facebook": "^3.2.0",
"@uppy/file-input": "^3.0.4",
"@uppy/google-drive": "^3.4.0",
"@uppy/image-editor": "^2.4.0",
"@uppy/onedrive": "^3.2.0",
"@uppy/progress-bar": "^3.0.4",
"@uppy/url": "^3.5.0",
"@uppy/webcam": "^3.3.4",
2

Are you hosting Companion yourself? You need a Companion instance for @uppy/url.

3

Yes, I am hosting Companion myself. I have use the same Companion in different applications, one works while the other doesn’t.

The set up on client side is the same, and the S3 bucket used is also the same. I am not sure where else should I be looking into at this point, as the issue seems to be internally from Uppy.

4

I have tried to upgrade my Uppy version to the latest today, but the result is pretty much the same, except that the payload from websocket returns with a different message:

{
  "action": "error",
  "payload": {
    "error": {
      "name": "TypeError",
      "message": "Cannot read properties of null (reading 'query')"
    }
  }
}
5

I can’t reproduce this on https://uppy.io/examples. Without a reproducible example I don’t think I can look into this.

6

Would the screenshot of the looping requests in the network tab help? I can also take a screenshot of the initiator as well.