-
Notifications
You must be signed in to change notification settings - Fork 55
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
W.createUpload is not a function #295
Comments
I have the same error with 2.1.1. Have you found a solution for this? |
Are you using |
I have the error in a self hosted studio (Netlify) and not embedded in Next.js |
Mine was hosted with sanity deploy as a standalone project. I was getting this error in both local and deployed. Bizarrely, it "disappeared" for me -- I did not fix it, but I dread it coming back. |
Now I am getting xDr.createUpload is not a function when deployed to vercel and W4.createUpload is not a function locally. |
I am using signed urls |
please help this makes the plugin completely dead for me :( |
i changed absolutely nothing but it is working now. this must be an intermittent issue. |
@sharpsteelsoftware could you open |
I face the same problem with the latest version of Sanity and this plugin (2.2.2) :
|
but I also got it on 2.2.2 |
I also am getting this error except I'm receiving it as "W4.createUpload is not a function" I am in a similar situation to @sharpsteelsoftware where I had not changed anything. On my Mux log it repeatedly says Video.upload.created and video.upload.cancelled |
Hey guys, After fiddling with this for a couple hours I found that downgrading to @2.0.16 caused the issue to disappear. Obviously not an ideal solution for those who want to have their source code up to date but hopefully sanity/mux can resolve this together. |
With v.2.2.3 I don't have the issue anymore. |
I don't either but I have gone through this process a few times where it seemingly appears and disappears. I am worried it will come back. |
I feel this relates to how the plugin interacts with a newer version of Sanity or associated library. I'd recently updated Sanity from 3.12 to 3.16, and updated the plugin and it's not working there. When I go back to an old package.json and package-lock.json file, everything works. That's using the old Mux interface. For me, rolling back even to Mux input version 2.0.17 didn't solve the problem. |
It started happening to me again. I did run ncu -u (node check updates) to update package.json. Unfortunately, even after reverting (and deleting node_modules), and even when deploying the old versions, I am still getting this. Maddening! |
OK I got it working. I had to remove the yarn.lock file as well as the node_modules and then revert package.json. this is working
this is not
|
Thanks @sharpsteelsoftware! |
Hi, I'm also struggling with this. Errors in the GUI:
From the console:
Full stacktrace:
I've tried different versions of the
Hope this can help the debugging 🤞 EDIT: I can also add that the logs in the Mux dashboard indicates that the upload is initiated, but then cancelled through an API request. I guess this could indicate that there's something going on client side: ✅ EDIT 2: I found that v2.0.17 works with the newest version of Sanity (v3.23.4). So downgrading to this version could be a viable workaround while waiting for a solution to this. |
Had the same issue with v2.2.3, but upgrading to v2.2.4 solved it for me :) |
Plugin was working fine now I am getting this crash anytime I upload a video.
"sanity-plugin-mux-input": "^2.1.0",
The text was updated successfully, but these errors were encountered: