XHRUpload seems to be not working when using Companion server

[MiloszKrajewski]

Using uppy companion server and client using Tus for upload works fine.

Unfortunately I need to use XHRUpload in one case, and this seems to be not working at all.
When uploading file from "my device" everything work great (so XHR upload is configured properly) but when trying to upload from "Link" after pressing Upload button nothing happens: progress indication is spinning forever and no network activity (debug tools) is observed.

Am I doing it wrong? Or it is just not supported?

Thanks,
Milosz

[arturi]

Confirmed the bug, we are looking into it, thanks for reporting!

[arturi]

The bug has been fixed by:
de04c79 and c1abfea

[KhalilMohammad]

Are npm packages updated?

[arturi]

@KhalilMohammad Not yet, a release likely coming this week.

[goto-bus-stop]

Looks like this was released in 1.0.0. Thanks!

[gabbanaesteban]

I'm using 1.0.2 and the issue still happening again.

[MiloszKrajewski]

In my case: 1.0.0 frontend -> 1.0.0 uppy works fine but 1.0.0 -> 1.0.1 does not. 1.0.1 -> 1.0.1 works again.
I did not try 1.0.2 but my suggestion would be to test if you have matching frontend/backend versions.
NOTE: I'm talking about GoogleDrive/Dropbox/Instagram as I'm not using Link anymore.

[gabbanaesteban]

I tried 1.0.0 but couldn't connect to Google Drive using that version.

[arturi]

@gabbanaesteban, @MiloszKrajewski

In my case: 1.0.0 frontend -> 1.0.0 uppy works fine but 1.0.0 -> 1.0.1 does not.

If you are experiencing issues with authentication with Google Drive or Instagram, it is due to a breakage of backwards-compatibility we’ve accidentally introduced in @uppy/companion@1.0.1.

The fix was released yesterday on npm as @uppy/companion@1.0.2, see #1564 for details.

Please update @uppy/companion to v1.0.2 for backwards-compatibility with Uppy Client ^1.0.0, @uppy/companion@1.0.1 is now deprecated.

Sorry about the trouble! Please do let us know if the issue is resolved for you.