Dynamic server usage: Route /posts couldn't be rendered statically because it used cookie

[cloud crow]

can someone help me?
I had my next.js application structured like: /app/[locale]/[lang]/**, but then I removed the locale and lang and now I have some issues like this one:
Dynamic server usage: Route /posts couldn't be rendered statically because it used cookies

If I add the locale and lang folders again the errors disappear

I already deleted the .next folder and ran the script again. The error persists...

[light forge]

Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

[sudden juniper]

remove both folders. Now check where you are using the cookies function (maybe you saved your locale inside the cookies or somiliar). Just check where you used it.

After that check if the route where the cookies are called was rendered statically. If so, either make it dynamic or remove the cookie function

[cloud crow]

both folders?

and what do you mean by saving the locale with the cookies func?

[sudden juniper]

yea, the locale and the lang folder, that you mentioned.

[cloud crow]

I already deleted them

[sudden juniper]

it was just an expression so you might know where the error comes from

[sudden juniper]

great

Now check where you are using the cookies function (...). Just check where you used it.

[cloud crow]

well that's fun bcs in the posts page I don't use cookies

it seems like I fixed. when I run the build script locally it works fine, but the pipeline is always failing

⨯ useSearchParams() should be wrapped in a suspense boundary at page "/auth". Read more: https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout

I mean, wth

why would I need to do this?

[sudden juniper]

Reading search parameters through useSearchParams() without a Suspense boundary will opt the entire page into client-side rendering. This could cause your page to be blank until the client-side JavaScript has loaded.

So you might want to wrap your Component that uses useSearchParams inside a suspense boundary like:

<Suspsense fallback={<p>Some Fallback</p>}>
  <ComponentThatNeedsSearchParams />
</Suspense>

[cloud crow]

but why I don’t have this error locally?

[sudden juniper]

idk. Wrap it with a suspense boundary and you are good to go 👍

[cloud crow]

yeah it makes sense

i appreciate ur help

[light forge]

✅ Success!

This question has been marked as answered! If you have any other questions, feel free to create another post

Jump to answer

[Click here](#1312031724296998952 message)