Prop id
did not match. Server: "toggle--gxfg3t7xwo" Client: "toggle--ki0j10p2l"
#11998
Unanswered
nicholaschiang
asked this question in
Help
Replies: 1 comment
-
Just investigated this but it seems related to some component somewhere using a css-in-js solution for which you don't have the server-side component implemented. I couldn't find exactly where but it seems related to the checkbox (because there's a toggle class) https://github.com/tutorbookapp/covid-tutoring/blob/fece458c9928e975584d2a8f51882ab061a6bc71/src/schedule-input/lib/schedule-input.tsx#L2 I've converted this to a discussion as it's not a bug in Next.js. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It seems like Next.js isn't correctly rendering my
ScheduleInput
component such that it keeps throwing this warning on page load:To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Expected behavior
A clear and concise description of what you expected to happen.
Those two props should match. That
ScheduleInput
component is correctly defined insrc/schedule-input/lib/schedule-input.tsx
; I have no idea why it's throwing this error.System information
Browser (if applies): Firefox
^9.3.4
12.16.1
Beta Was this translation helpful? Give feedback.
All reactions