Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code.

react-dom.development.js:530 Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://fb.me/react-unsafe-component-lifecycles for details.

Move data fetching code or side effects to componentDidUpdate.
If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state

Please update the following components: AutosizeInput, Select

same error with 3.1.0 for me:

Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code

For me too! Same warning...

Also getting the same error in 3.1.0....

The same error in 3.1.0

@razh

See also:

UNSAFE_componentWillReceiveProps
Legacy context API: MenuPlacer

#3720 (comment)

@razh There is currently a rewrite in progress to remove these deprecated lifecycle methods.

I'm getting an error, not just a warning.
index.js:1 Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://fb.me/react-unsafe-component-lifecycles for details.

Move data fetching code or side effects to componentDidUpdate.
If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state

Please update the following components: AutosizeInput, Select

In addition to the above, I am getting this one after I start selecting something:

index.js:1 Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of NodeResolver which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://fb.me/react-strict-mode-find-node
    in div (created by Context.Consumer)
    in EmotionCssPropInternal (created by MenuList)
    in MenuList (created by MenuPlacer)
    in ScrollBlock (created by MenuPlacer)
    in NodeResolver (created by ScrollCaptor)
    in ScrollCaptor (created by ScrollCaptorSwitch)
    in ScrollCaptorSwitch (created by MenuPlacer)
    in div (created by Context.Consumer)
    in EmotionCssPropInternal (created by Menu)
    in Menu (created by MenuPlacer)
    in MenuPlacer (created by Select)
    in div (created by Context.Consumer)
    in EmotionCssPropInternal (created by SelectContainer)
    in SelectContainer (created by Select)
    in Select (created by StateManager)

Hi all,

Thank you to everyone who has provided information above.

As you may be aware, this bug has been reported multiple times as per issue #4094. On behalf of the maintainers I apologise it's taken awhile to get to this.

A new master issue #4094 has since been created to help keep track of this bug going forward.

This new issue will exist as the source of truth going forward to investigate the issue, report findings, and implement a bug fix.

We'll take into account all the details above while investigating.

If you feel this issue has been wrongly closed as it isn't related to the new master issue #4094, please let us know and we'll take another look.

Again, thank you.

In version 3.1.0 this warning is shown

@JanaSundar

@JanaSundar Follow #4094 to get the latest updates on this issue.

Any updates for this bugs?

I've already bug in new blank project.


* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://reactjs.org/link/derived-state

Please update the following components: AutosizeInput, Select```

@junreyd

@junreyd and @golendercaria

Regarding an update on this, fixes for these issues are a priority. We've identified and resolved these (thanks to @Methuselah96) in the least intrusive ways possible, and are preparing a new release likely within the next week or two. You can read more about it here. #4293 (comment)

anyone can help me, I got this error too

@fadzrinmadu

Greetings @fadzrinmadu ,

This issue was closed with the release of version 4. Can you please confirm which version of react-select you are using?

for me it's a react 18 dependency mismatch, it could be anything. Update depends in your package.json

Navigation Menu

Repository navigation

Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. #3915

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. #3915

Description

Activity

maximilianschmidt commented on Mar 25, 2020

lucasltv commented on Apr 1, 2020

JoeGreen1982 commented on Apr 2, 2020

codewhynot commented on Apr 7, 2020

0xdevalias commented on Apr 22, 2020

giacintayao commented on Jun 12, 2020

gempain commented on Jun 15, 2020

bladey commented on Jun 18, 2020

JanaSundar commented on Aug 12, 2020

Methuselah96 commented on Aug 12, 2020

junreyd commented on Sep 1, 2020

golendercaria commented on Dec 12, 2020

ebonow commented on Dec 12, 2020

fadzrinmadu commented on Apr 23, 2021

ebonow commented on Apr 23, 2021

shopglobal commented on Apr 28, 2023

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions