Peter Gerhat Peter Gerhat - 2 months ago 78
React JSX Question

React Native: No propType for native prop RCTView.maxHeight

After upgrading to RN 0.30 I started seeing the error shown below even when building the simplest possible app:

react-native init AwesomeProject
react-native run-ios



  • The strangest is that components
    BlurView
    ,
    VibrancyView
    and
    RNSearchBar
    are included in the warning messages despite the project not using them.

  • Recompiling/cleaning the project doesn't fix the problem.



Console & error:

2016-07-22 08:48:02.985 [warn][tid:main][RCTEventEmitter.m:52] Sending `websocketFailed` with no listeners registered.
2016-07-22 08:48:03.031 [warn][tid:com.facebook.react.JavaScript] Warning: Native component for "BlurView" does not exist
2016-07-22 08:48:03.032 [warn][tid:com.facebook.react.JavaScript] Warning: Native component for "VibrancyView" does not exist
2016-07-22 08:48:03.033 [warn][tid:com.facebook.react.JavaScript] Warning: Native component for "RNSearchBar" does not exist
2016-07-22 08:48:03.040 [error][tid:com.facebook.react.JavaScript] `Constructor` has no propType for native prop `RCTView.maxHeight` of native type `CGFloat`
If you haven't changed this prop yourself, this usually means that your versions of the native code and JavaScript code are out of sync. Updating both should make this error go away.
2016-07-22 08:48:03.043 [fatal][tid:com.facebook.react.RCTExceptionsManagerQueue] Unhandled JS Exception: `Constructor` has no propType for native prop `RCTView.maxHeight` of native type `CGFloat`
If you haven't changed this prop yourself, this usually means that your versions of the native code and JavaScript code are out of sync. Updating both should make this error go away.
2016-07-22 08:48:03.102 [error][tid:com.facebook.react.JavaScript] Module AppRegistry is not a registered callable module.
2016-07-22 08:48:03.104 [fatal][tid:com.facebook.react.RCTExceptionsManagerQueue] Unhandled JS Exception: Module AppRegistry is not a registered callable module.


screenshot

Answer

The reason for this error was that another instance of React packager (still on 0.28) was running in the background at the time after I updated to 0.30.

Restarting React packager solved the problem.

Comments