When I upload a file from device (from Uppy web control) (using Uppy-Companion-Tus) the Uppy control request several OPTIONS to Tus endpoint and throw this exception.
With other providers the control works well.
Any idea what can happen?
Thanks in advance.
Matias Creimerman
Hi Matias,
I have no direct solution to what you cause this.
What tus server are you using? Please also provide your code and steps to reproduce this.
I believe I have the same issue.
The file on the server is gone, but the key/item still exists in localStorage.
The CORS errors I cannot explain. A side effect I presume.
Problem seems to be that Uppy is trying to resume an upload that no longer exists on the server. Use your browser console to clear the key from local storage and the issue goes away.
I came here looking for a production solution. What are we to do? “After the fact” or “Proactive”?
Proactive: cycle thru localStore, sends keys to server, confirm they exist.
After the fact: confirm with server file is gone and delete localStorage item and restart.
After the fact is easier, but then must wait for all the COS errors and delays before getting a failure notice. Proactive may be faster/nicer experience for user.
Figuring out your own personal recipe for uppy+tusd seems to be the hard part.
“With great flexibility comes great responsibility (and confusion and testing)”.
Cheers.
Hi Hank,
tus-js-client (which is used by Uppy) already implements the “after the fact” approach. If it’s not capable of resuming an upload because the server has deleted it, it will remove the entry in localStorage and start a new upload.
However, I cannot decipher from your post what actual problem you are facing.