question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[V2] Warning: Prop `id` did not match.

See original GitHub issue

Getting this error in console.

Warning: Prop id did not match. Server: “react-select-5-input” Client: “react-select-2-input”

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:22

github_iconTop GitHub Comments

49reactions
KidkAroliscommented, May 22, 2018

I think it’s instanceId prop, not id prop?

31reactions
bkyamcommented, Apr 28, 2020

I’m building out a site with Nextjs, and found that passing inputId fixed the issue.

<Select
				id={this.props.id}
				instanceId={this.props.instanceId}
				inputId={this.props.instanceId}
				defaultValue={this.props.options[`${this.props.defaultValue}`]}
				isDisabled={this.props.isDisabled}
				isFocused={this.props.isFocused}
				isSelected={this.props.isSelected}
				onChange={this.handleChange}
				name={this.props.name}
				options={this.props.options}
				menuPlacement='auto'
				components={{ DropdownIndicator }}
				styles={theme == 'dark' ? darkStyle : lightStyle}
			/>

Read more comments on GitHub >

github_iconTop Results From Across the Web

Recharts - Warning: Prop id did not match. Server: #12863
This is a generic Next.js warning that happens when the DOM in the client does not exactly match the DOM that was rendered...
Read more >
react-select: How do I resolve “Warning: Prop `id` did not match”
Select component needs an instanceId, id mandatory So Just add. id="long-value-select" instanceId="long-value-select". to your Select component it will ...
Read more >
react-aria-ssr-id-bug - CodeSandbox
Sign in. Sandbox Info. react-aria-ssr-id-bug. Console warns with: Warning: Prop id did not match. Server: "react-aria-1" Client: "react-aria-2".
Read more >
Solving the Styled Components Warning in Next.JS with Babel
Warning : Prop `className` did not match. Server: “fs-fdsf” Client: “sd-dfasj”. The combination of Next.JS and Styled Components is truly ...
Read more >
Prop `id` did not match. Server: "reactHubspotForm4" Client ...
I have embedded the Hubspot script in my Next.js project. But now every time I refresh the page locally I get the error...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found