client error: Objects are not valid as a React child

[chaotic-justice]

Description

develop branch works fine locally. on deployment, it was working fine for awhile until it becomes a blank screen w/ message "Application error: a client-side exception has occurred while loading xxx.vercel.app (see the browser console for more information)."

browser console:
[Error: Objects are not valid as a React child (found: object with keys {en, es}). If you meant to render a collection of children, use an array instead.]

created a new branch by checking out develop and git reset --hard to a previous commit 2804bf3 (or earlier) which i am sure it worked earlier, still results in same error.

Verifications

• I've verified that the problem I'm experiencing isn't covered in the docs.
• I've searched for similar, existing issues on GitHub and Stack Overflow.
• I've compared my app to a working example to look for differences.

Mandatory reproduction URL

https://github.com/chaotic-justice/osmanthus-kagi

Reproduction description

Steps to reproduce:

1. set your credentials listed on .env.example
2. checkout to develop branch
3. run pnpm install then run pnpm dev
4. it should work locally, then deploy it to vercel the build will succeed but it will result in client error
5. or checkout to diagnostic branch, several commits behind develop, which i know for sure it worked before and repeat those steps

Expected behaviour

blank screen w/ error message even if you roll back to a previous working commit (once deployed)

[amannn]

which i am sure it worked earlier, still results in same error.

Hey, this seems more like a usage question. You might want to dig a bit further into this and if in doubt, compare your implementation with a working example.

If you're able to pinpoint a specific issue in next-intl based on the reproduction template then I'm happy to have a look, but I hope you can understand that I can't generally analyze and debug your app for errors.

I'll move this to a discussion for the time being.

[chaotic-justice]

will look into it, thanks. i think it may be a payload issue, similar error encountered by a payload user