Skip to content
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.

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

[BUG:] React view error after successfully log-in #30

Open
tomasete opened this issue Mar 22, 2024 · 0 comments
Open

[BUG:] React view error after successfully log-in #30

tomasete opened this issue Mar 22, 2024 · 0 comments
Labels

Comments

@tomasete
Copy link

tomasete commented Mar 22, 2024

Describe the bug

Just after going thru the set up steps, and attempt the first user login I had the following error displayed and could´t continue testing the app:

Unhandled Runtime Error

Error: Objects are not valid as a React child (found: [object Error]). If you meant to render a collection of children, use an array instead.

Steps to reproduce

  1. Install the app following the getting started steps
  2. Run the application using the next dev command
  3. The log in-register screen is displayed
  4. I create a user successfully
  5. After log-in the following error is shown
Unhandled Runtime Error

Error: Objects are not valid as a React child (found: [object Error]). If you meant to render a collection of children, use an array instead.
Call Stack
throwOnInvalidObjectType
(app-pages-browser)\node_modules\next\dist\compiled\react-dom\cjs\react-dom.development.js (8884:0)
reconcileChildFibersImpl
(app-pages-browser)\node_modules\next\dist\compiled\react-dom\cjs\react-dom.development.js (9891:0)
reconcileChildFibers
(app-pages-browser)\node_modules\next\dist\compiled\react-dom\cjs\react-dom.development.js (9912:0)
reconcileChildren
(app-pages-browser)\node_modules\next\dist\compiled\react-dom\cjs\react-dom.development.js (15627:0)
updateHostComponent$1
(app-pages-browser)\node_modules\next\dist\compiled\react-dom\cjs\react-dom.development.js (16589:0)
beginWork$1
(app-pages-browser)\node_modules\next\dist\compiled\react-dom\cjs\react-dom.development.js (18427:0)
beginWork
(app-pages-browser)\node_modules\next\dist\compiled\react-dom\cjs\react-dom.development.js (26791:0)
performUnitOfWork
(app-pages-browser)\node_modules\next\dist\compiled\react-dom\cjs\react-dom.development.js (25637:0)
workLoopSync
(app-pages-browser)\node_modules\next\dist\compiled\react-dom\cjs\react-dom.development.js (25353:0)
renderRootSync
(app-pages-browser)\node_modules\next\dist\compiled\react-dom\cjs\react-dom.development.js (25308:0)
performConcurrentWorkOnRoot
(app-pages-browser)\node_modules\next\dist\compiled\react-dom\cjs\react-dom.development.js (24432:0)
workLoop
(app-pages-browser)\node_modules\next\dist\compiled\scheduler\cjs\scheduler.development.js (256:0)
flushWork
(app-pages-browser)\node_modules\next\dist\compiled\scheduler\cjs\scheduler.development.js (225:0)
performWorkUntilDeadline
(app-pages-browser)\node_modules\next\dist\compiled\scheduler\cjs\scheduler.development.js (534:0)

This happens in different environments: Windows, Linux, etc

Browsers

Chrome, Firefox

Additional context (Is this in dev or production?)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant