Max Cherniavskyi

Wrapping in CacheProvider has helped in my case: ```js const myCache = createCache({ key: "cache-key" }); function MyApp({ Component, pageProps }: AppProps) { return ( ); } ```

@Lucifier129 Thank you for checking. I'll try to isolate this bit of code and try again.

https://github.com/lazytiger/gumbo-query/commit/c5bb4e9237819cf2d57909ba9b2730d5cfa1e660#diff-116856bc935ab49f13924ac73743e89eR26 Add libgumbo.so

Here's a reproducible example: https://stackblitz.com/edit/nextjs-fznkmq?file=package.json,next.config.js I've narrowed it down to the options `swcMinify` and `next` version `12.3.1`. Steps to reproduce: 1. Set `swcMinify: true` in next.config.js. 2. Run `yarn &&...

Tried that myself again and couldn't reproduce either. However, when I tried `npx next build && npx next start` instead, the error appeared again:

Thanks for debugging. I've referenced your find in this thread: https://github.com/vercel/next.js/discussions/30237#discussioncomment-3755143

Seems like the issue is fixed on canary: https://github.com/vercel/next.js/discussions/30237#discussioncomment-3769166

> State represents user interaction. If there was no user interaction, why is state being set? Nothing "happened". A common reason for changing the app state before hydration finishes is...

Before raising this issue, I set up a reduced example with context only but without zustand and it worked as expected.

@dai-shi Here's an example without zustand: https://stackblitz.com/edit/nextjs-b6vatg?file=app%2FContextProvider.js