-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undefined "uploadRemoteFile" when using RemoteSources #4791
Comments
Hi! Sorry to hear you are facing this issues. Could you try removing the lock file and doing |
we have tested latest version uppy and subdependencies and the problem does not exist. so the solution is to upgrade recursively all dependencies of uppy. closing this |
Hello @mifi , I have same issue |
"@uppy/core": "^3.7.1", |
@mifi, After upgrading also I have same issue. Code: |
Does it happen locally or only on Codesandbox? We think Codesandbox is resolving dependencies incorrectly. What might help is adding |
Upgrade all uppy dependencies recursively, or delete yarn.lock/package-lock.json if you don’t know how to do that. |
@mifi , We have tried upgrading uppy dependencies recursively. As u suggested, yarn lock file also deleted. We cross verified node_modules version as well. It is updated to latest version. I'm experiencing the same in local setup, @arturi suggested to setup local because Codesandbox is resolving dependencies incorrectly. Drive Link ( I have added package and yarn lock file) Kindly check and tell us a work around at least. |
Thanks for your detailed description. I see in your yarn.lock file that Can you double check inside node_modules/@uppy/provider-views/package.json that "version" is set to "3.7.0"? also node_modules/@uppy/provider-views/lib/View.js that this line exists:
|
Yes that line exists, added the file link below |
this is very strange. I cannot reproduce this locally. Are you using your own companion server? Any chance that you could share a minimal reproducible example (without any of your secret keys)? or a codepen for example (codesandbox has problem with dependency resolution) |
We are using transloadit companion server. |
ok! now i managed to reproduce the problem, thanks! |
🥹 |
for some reason, only when testing locally using VITE_COMPANION_URL=https://api2.transloadit.com/companion only we get this error... i'm thinking for some reason, the remote file gets serialized into state and then de-serialized again causing remote.requestClient to be gone so I solve it by instead storing the request clients in Uppy fixes #4791
created a pr #4814 |
This issue is blocking us, kindly provide the update or any workaround if possible. |
hi! hoping to merge that PR today |
* fix uploadRemoteFile undefined for some reason, only when testing locally using VITE_COMPANION_URL=https://api2.transloadit.com/companion only we get this error... i'm thinking for some reason, the remote file gets serialized into state and then de-serialized again causing remote.requestClient to be gone so I solve it by instead storing the request clients in Uppy fixes #4791 * fix bugs * remove unrelated space changes * apply suggestions * Update Uppy.js * fix lint --------- Co-authored-by: Antoine du Hamel <[email protected]>
Initial checklist
Link to runnable example
No response
Steps to reproduce
I am using Svelte & SvelteKit with Uppy set up in an action:
I tried to revert to previous versions but still had the same issue. Current versions:
before our app update yesterday (tried, the issue still persists):
Expected behavior
Should upload files from Google or Dropbox.
Actual behavior
Console error and file is not uploaded.
[Uppy] [16:21:39] TypeError: can't access property "uploadRemoteFile", file.remote.requestClient is undefined
The text was updated successfully, but these errors were encountered: