Getting proptype warning errors for FB components
See original GitHub issueSince upgrading to 0.30.0, we are now getting many, many warnings not to manually call React.Proptypes validation functions. But these are not in our code, they’re in RCT code.
Two of many:
ExceptionsManager.js:76 Warning: You are manually calling a React.PropTypes validation function for the borderBottomRightRadius
prop on RCTImageView
. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.
ExceptionsManager.js:76 Warning: You are manually calling a React.PropTypes validation function for the translateY
prop on TouchableHighlight
. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.
We’ve updated all our modules, so…
Issue Analytics
- State:
- Created 7 years ago
- Reactions:14
- Comments:16 (9 by maintainers)
The fix is to use the version of React that is specified by
For RN 0.30 and 0.31:
npm install react@~15.2.1
For RN 0.32:npm install react@~15.3.0
That’s why you should stick to required peer dependencies: react-native requires
react@~15.2.0
, which does not include react 15.3, only versions >= 15.2 and < 15.3 (even if I also tried it haha). This change from^
to~
was recently introduced in react-native to avoid this kind of issue.