Error: Sanity LocaleContext value missing. Is this hook being used outside LocaleContext.Provider? about sanity HOT 12 CLOSED

I got the same error this morning after starting a blank Sanity project using sanity init.

I rolled Sanity (and Vision) back to 3.36.0 and the issue went away.

from sanity.

Same issue here.

from sanity.

MatsCornegoor

Yep! Seems like a bug with 3.36.1.

from sanity.

I ran into the same problem after the Sanity update. I reinstalled as above to 3.36.0 but nothing changed. The same error is displayed "Uncaught error: Sanity LocaleContext value missing. Is this hook being used outside LocaleContext.Provider?"
"dependencies": {
"@sanity/vision": "^3.36.0",
"react": "^18",
"react-dom": "^18",
"react-icons": "^4.11.0",
"react-is": "^18.2.0",
"sanity": "^3.36.0",
"styled-components": "^6.1.8"
},

from sanity.

Hello @aquamarineru ! It should be 3.36.2 rather than 3.36.0. You can double-check by running npm ls sanity to verify which version you're running (feel free to put that output in this thread as well)!

You can either change your package.json to:

"dependencies": {
"@sanity/vision": "^3.36.2",
//..the rest of your packages...
"sanity": "^3.36.2",
}

Or use something like https://www.npmjs.com/package/npm-check-updates to update packages.

Please let me know!

from sanity.

I'm getting the same error this morning

from sanity.

Me too

from sanity.

I tried rolling back like @pixeldust suggested, but the issue still persists. Could this be a bug inside the dataset? I also created the dataset this morning using sanity cli

from sanity.

I had the same issue, did what @pixeldust suggested and rolled back to 3.36.0 for both Sanity and Sanity Vision.

from sanity.

I tried rolling back like @pixeldust suggested, but the issue still persists. Could this be a bug inside the dataset? I also created the dataset this morning using sanity cli

whoops, I just reinstalled sanity and rolling back to 3.36.0 does work!

from sanity.

Hello all! This was indeed a bug in 3.36.1. 3.36.2 was just released, which should hopefully resolve this error.

from sanity.

Hello cngonzalez
Thank you very much after updating to the latest version everything worked

from sanity.