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
Desk crashes with Uncaught Error: Workspace: missing context value #724
Comments
Same problem |
I'm hitting this issue as well when trying to create a custom nav bar using the instructions at https://www.sanity.io/docs/studio-components-reference#db9fc60782a3 npm v10.2.3 |
I just had this issue happening quite randomly on a Remix project with an embedded Studio. No work was being done on the Sanity schemas or setup when it started happening. It would crash when i went to add new content on a Sanity document. |
Same here
Worked before updating, now i get |
Running into the same issue with my project, Has anyone found a workaround? |
Same here |
Describe the bug
When embedding the studio into a Next.js app, the desk tool crashes and throws an error "Uncaught Error: Workspace: missing context value". What's interesting is that I have 2 identical projects and one of them works fine, the other crashes with the mentioned error. If I build the studio separately and go to localhost:3333/studio, it doesn't crash.
What could be the issue?
To Reproduce
Steps to reproduce the behavior:
sanity.config.ts
Expected behavior
No error is thrown.
Screenshots
If applicable, add screenshots to help explain your problem.
Which versions of Sanity are you using?
Sanity v3.19.0
Next.js both v13.5.5 and v14.0.1
What operating system are you using?
macOS 14.1
Which versions of Node.js / npm are you running?
Run
npm -v && node -v
in the terminal and copy-paste the result here.Node.js v18.18.2
pnpm v8.10.0
Additional context
Add any other context about the problem here.
Security issue?
Any security issues should be submitted directly to security@sanity.io. In order to determine whether you are dealing with a security issue, ask yourself these two questions:
The text was updated successfully, but these errors were encountered: