Uppy: uploaded y/n

[musicformellons]

I uploaded files to the master.tus.io endpoint. Now I change to my proprietary endpoint and then it works for new files, but files already uploaded to master.tus.io are considered 'already uploaded' (but all progress is still at zero, which is also a bit odd). It looks like after cleaning the browser cache this persists. In browser cognito mode it works as expected, i.e. files are uploaded to my proprietary endpoint.

Question: what determines whether uppy considers a file as already uploaded?

[goto-bus-stop]

Most likely this is because of tus-js-client's resume option—when enabled, it stores data about the file and the endpoint in localStorage, so that it can pick the upload back up if it was interrupted. When you change the endpoint option, the old URLs are still in localStorage. Doing localStorage.clear() in your browser console should fix it. If you don't need to be able to pick up the upload again later, you can set resume: false in the Tus plugin options.

We could mitigate this in Uppy by setting the fingerprint() option in tus-js-client and adding in the endpoint URL, that's probably a good thing to do regardless.

[musicformellons]

Yeah, localStorage.clear() works!

I think adding in the endpoint URL is essential, otherwise when uppy gets popular and widespread the first endpoint upload will 'hijack' subsequent uploads of the upload-file to other endpoints.

[arturi]

@Acconut what do you think?

[Acconut]

That sounds like a good improvement, in particular since this is not the first time someone steps into this pit. I added it to my backlog but if someone wants to work on this quick fix in the meantime, I am happy to assist.

[Acconut]

FYI, since https://github.com/tus/tus-js-client/commit/2f8c14363bf040f91dd1adbe94ec7082db0b7513 the endpoint will be included in the fingerprint. It will be release in the next version soonish.