Network error when using the official uploader UI

Follow

New post

oreolek

• August 24, 2017 10:22

The official uploader UI (React included version) gives "A network error" on each upload try.

 

What happens (as seen in the dev tools) is: it starts the upload, makes a call to

https://upload.box.com/api/2.0/files/content

with file size, gets 404 (file not found BECAUSE IT WASN'T UPLOADED YET) and decides it's a network error.

 

I changed a line in the uploader source code from 

 

this.uploadPreflight()

to

this.uploadPreflightSuccessHandler(e))

in the upload function.

And now it meets a network error after the upload is finished. (The file is not uploaded anyway)

Uploader is at version 1.0.2

 

0

• 

  tonyjin

  • August 24, 2017 15:58

  Hello oreolek, do you have some sample code for your use case? You can also try plugging in your developer token and folder ID into the sample CodePen here: https://codepen.io/box-platform/pen/QvqGwr

   

  The first call to https://upload.box.com/api/2.0/files/content is correct since that's how the Box Upload File API works (https://developer.box.com/reference#upload-a-file). The preflight call checks whether the file you want to upload will be accepted by Box before you have to send the bytes over the wire.

  0

  Comment actions Permalink
• 

  oreolek

  • August 24, 2017 18:15

  Tried it on CodePen (folderId: 0). Still a network error.

  0

  Comment actions Permalink
• 

  tonyjin

  • August 25, 2017 12:00

  Two possibilities that I can think of:

   

  • Have you added the domains of both your app and the two needed by CodePen (https://s.codepen.io and http://s.codepen.io) to the CORS whitelisted domains in your application configuration? See: https://developer.box.com/docs/box-content-uploader#section-cross-origin-resource-sharing
  • Make sure the folder ID is a string and not an integer (e.g. use '0'). The fact that we don't support integers isn't great so we'll update this to support both numbers and strings in a later release.

  0

  Comment actions Permalink
• 

  oreolek

  • August 28, 2017 02:35

  Added the domains to CORS and converted folder ID to string. I even changed my Internet provider to open all ports and get a white IP.

  Still a network error.

  0

  Comment actions Permalink
• 

  tonyjin

  • August 28, 2017 11:22

  That's unfortunate. Do you mind sharing a screencast of your process with the network panel open? Otherwise a screenshot of the network error with the network panel and console logs both visible works as well.

   

  Example:

  

  0

  Comment actions Permalink

Please sign in to leave a comment.