Warning : componentWillReceiveProps has been renamed, and is not recommended for use. #3745

Activity

1. dicrescenzoa commented on Aug 30, 2019

   

   dicrescenzoa

   on Aug 30, 2019

   Last edited by dicrescenzoa

   More actions

   the same warning message is happening for jest as well.

   `console.warn node_modules/react-dom/cjs/react-dom.development.js:11494
   Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks 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
     * Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.
     
     Please update the following components: AutosizeInput, Select
   

   `

   package.json

   {
     "react": "^16.8.6"
     "jest": "^24.8.0",
     "react-select": "^3.0.4",
   }

   👍React with 👍5Reacted by Kiran Kalyan, Wait4Code, prince516, Chen and Maurice Dalderup
2. jarleriksen commented on Aug 31, 2019

   

   jarleriksen

   on Aug 31, 2019

   More actions

   Check #3720
3. mreishus commented on Oct 24, 2019

   

   mreishus

   on Oct 24, 2019

   More actions

   Still getting warning messages as of 3.0.8. This will prevent the new react concurrent mode (not released yet) from working.

   To reproduce, wrap your app in <React.StrictMode></React.StrictMode> tags.

   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
   

   👍React with 👍5Reacted by Drew Terry, Immo Sanders-Sjuts, Maurice Dalderup, Glenn 'devalias' Grant and Anecha Kuekharem
4. DalderupMaurice commented on Jan 3, 2020

   

   DalderupMaurice

   on Jan 3, 2020

   More actions

   Still getting warning messages as of 3.0.8. This will prevent the new react concurrent mode (not released yet) from working.

   To reproduce, wrap your app in <React.StrictMode></React.StrictMode> tags.

   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 for me, wrapping it in StrictMode it is filled with warning.
   See my reply here for the exact warnings: #3751 (comment)

   👍React with 👍2Reacted by David Pordomingo and Markus Ruottu
5. makker commented on Apr 21, 2020

   

   makker

   on Apr 21, 2020

   More actions

   +1
6. 0xdevalias commented on Apr 22, 2020

   

   0xdevalias

   on Apr 22, 2020

   Last edited by 0xdevalias

   More actions

   See also:

   • Warning: componentWillReceiveProps has been renamed #3720
   • received following warning of componentWillReceiveProps has been renamed about 'Select': #3751
   • Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. #3915

   ---

   #3720 (comment)

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

   👍React with 👍1Reacted by Rall3n
7. bladey

   added

   issue/bug-unconfirmedIssues that describe a bug that hasn't been confirmed by a maintainer yetIssues that describe a bug that hasn't been confirmed by a maintainer yet

   on Jun 3, 2020
8. bladey commented on Jun 18, 2020

   

   bladey

   on Jun 18, 2020

   Contributor

   More actions

   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.
9. bladey

   closed this as completedon Jun 18, 2020