8000 application error: Objects are not valid as a React child · Issue #12460 · payloadcms/payload · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

application error: Objects are not valid as a React child #12460

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.

Sign up for GitHub

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

Jump to bottom
Closed
chaotic-justice opened this issue May 20, 2025 · 1 comment
Closed

application error: Objects are not valid as a React child #12460

chaotic-justice opened this issue May 20, 2025 · 1 comment

Comments

@chaotic-justice
Copy link
chaotic-justice commented May 20, 2025 •
edited
Loading

Describe the Bug

develop branch works fine locally. on deployment, it was working fine for a couple of commits after next-intl was installed, then 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)."

error persists after nuking my db, so i dont think is a db issue. if i create a new branch, git reset to the commit before next-intl was setup, re-deploy, then it works

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.]

what's strange: es isn't even listed on my next-intl / payload-i18n configs

Link to the code that reproduces this issue

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

Reproduction Steps

  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. try reverting to several commits earlier git reset --hard 0e6fa32 when next-intl was first set up, (which i know for sure it worked before), re-deploy => also same error

Which area(s) are affected? (Select all that apply)

Not sure

Environment Info

payload: 3.38.0
  next: 15.3.2
  @payloadcms/db-mongodb: 3.38.0
  @payloadcms/email-nodemailer: 3.38.0
  @payloadcms/email-resend: 3.38.0
  @payloadcms/graphql: 3.38.0
  @payloadcms/live-preview: 3.38.0
  @payloadcms/live-preview-react: 3.38.0
  @payloadcms/next/utilities: 3.38.0
  @payloadcms/payload-cloud: 3.38.0
  @payloadcms/plugin-cloud-storage: 3.38.0
  @payloadcms/plugin-form-builder: 3.38.0
  @payloadcms/plugin-nested-docs: 3.38.0
  @payloadcms/plugin-redirects: 3.38.0
  @payloadcms/plugin-search: 3.38.0
  @payloadcms/plugin-seo: 3.38.0
  @payloadcms/richtext-lexical: 3.38.0
  @payloadcms/storage-s3: 3.38.0
  @payloadcms/translations: 3.38.0
  @payloadcms/ui/shared: 3.38.0
  react: 19.1.0
  react-dom: 19.1.0
@chaotic-justice chaotic-justice added status: needs-triage Possible bug which hasn't been reproduced yet validate-reproduction Auto-added tag on create to tell bot to check recreation URL, removed after check. labels May 20, 2025
@github-actions github-actions bot removed the validate-reproduction Auto-added tag on create to tell bot to check recreation URL, removed after check. label May 20, 2025
@chaotic-justice
Copy link
Author

somehow it works on its own after a few days with no new changes

@github-actions github-actions bot removed the status: needs-triage Possible bug which hasn't been reproduced yet label May 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chaotic-justice
0