Getting Invalid prop `style` supplied to `Icon`.
See original GitHub issueMy Toast package version is 1.4.6.
During configuration (<Toast ref={ref => Toast.setRef(ref)} />
), I receive following error;
[Tue Feb 16 2021 23:27:09.100] ERROR Warning: Failed prop type: Invalid prop `style` supplied to `Icon`.
in Icon (at base/index.js:42)
in BaseToast (at success.js:9)
in SuccessToast (at src/index.js:18)
in RCTView (at View.js:34)
in View (at createAnimatedComponent.js:165)
in AnimatedComponent (at createAnimatedComponent.js:215)
in ForwardRef(AnimatedComponentWrapper) (at src/index.js:381)
in Toast (at App.tsx:48)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:6 (2 by maintainers)
Top Results From Across the Web
react-native - Failed prop type: Invalid prop `style` supplied to ...
I think FontAwesomeIcon is not a RN Text component as such, therefore fontSize is not an accepted prop. Use <FontAwesomeIcon ... size={5}> ...
Read more >invalid prop `rows` of type `object` supplied to `forwardref ...
Warning: Failed prop type: Invalid prop rows of type object supplied to ForwardRef(DataGrid), expected array.` Solution I believe the problem is in the...
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 >Using a multi line component with a constant inside a function?
This is failing with Failed prop type: Invalid prop children supplied to ForwardRef(Box) , expected a ReactNode. and the area of the ...
Read more >Typechecking With PropTypes - React
When an invalid value is provided for a prop, a warning will be shown in the JavaScript console. For performance reasons, propTypes is...
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
Sounds like a regression due to #147. I’ll fix it as soon as I can, thanks for raising it
I’m getting the same error. How can I fix it?