I am using restrictions in the uppy options and they are working fine, however by design they throw an error in the console. Is this the intended way for them to work?
It seems like catching the restriction using the .on(‘restriction-failed’, …) callback and alerting the user works as intended and should not throw an error.
Is there a way to catch or silence specific errors on restrictions?
Hi! I’ve fixed this issue in https://github.com/transloadit/uppy/pull/1726, and we’ve just released a new version of @uppy/core. Please update your plugins to the latest versions and let us know if this solves the issue.
Hi, I’m having the same problem.
I’m trying with:
uppy.on("restriction-failed", (file, error) => {
console.log(error)
return false
})
But it still throws an error when I try to add a file manually.
"@uppy/core": "3.0.1",
"@uppy/golden-retriever": "3.0.0",
"@uppy/react": "3.0.1",
"@uppy/tus": "3.0.1",
Hi, could you create a new issue with a reproducible example? That helps keeping track of bugs.
Sorry for the late reply. I didn’t get a notification.
I will create a new issue on github. No problem! Thanks