Invalid props.style key `NativeBase`
See original GitHub issuenode, npm, react-native, react and native-base version
“native-base”: “^2.7.2”, “react”: “16.4.2”, “react-native”: “0.56.0”,
Actual behaviour
When I am trying to use “Content” component I’m getting a error:
Code
render () {
return (
<Content/>
)
}
Info
Is the bug present in both iOS and Android or in any one of them?
I’ve checked only on Android.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:19 (5 by maintainers)
Top Results From Across the Web
Invalid props.style key `NativeBase` supplied to `ScrollView ...
ExceptionsManager.js:84 Warning: Failed prop type: Invalid props.style key `NativeBase` supplied to `ScrollView`.
Read more >React-Native: Native-base: failed prop type: Invalid props.style ...
It seems there is an issue in a file from the library you are using. They have nested a style inside another, thus...
Read more >Invalid props.style key 'textAlign' supplied to 'View'-Reactjs
Coding example for the question Failed prop type: Invalid props.style key 'textAlign' supplied to 'View'-Reactjs.
Read more >Utility Props - NativeBase
Style props are a way to alter the style of a component by simply passing props to it. It helps to save time...
Read more >Components - NativeBase
NativeBase gives you privilege to customize the props of this component. Example: To have custom style for button, include them in style prop...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing this tomorrow in case of no response
Not sure if I’m getting the same issue, but basically I have
This gives me that same error I think it’s due to the “opacity” on the Text.
However, if I switch to react native Text, no error…