Cannot read property 'setNativeProps' of undefined
See original GitHub issueHere is an image with the stack trace.
I get this error when I click on a TouchableWithoutFeedback
with a single View
. The press sets off an animation to bring up an Animated.View
overlay with a PickerIOS
inside. The error only happens about one in presses. If I close the red box, the app continues to operate correctly. Any idea what might be causing this?
I can try reproducing this in RN Playground if it might help.
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
TypeError: Cannot read property 'setNativeProps' of null #889
Hi, using the MapView component i got this error: TypeError: Cannot read property 'setNativeProps' of null at MapView.
Read more >Cannot read property 'setNativeProps' of undefined react-native
i have used react-native-drawer . i have kept the side menu file seperate and import it in main file . i want to...
Read more >Cannot read 'setNativeProps' of undefined. The sequel. | Voters
Cannot read 'setNativeProps' of undefined. The sequel. Voters | React Native. Cannot read 'setNativeProps' of undefined.
Read more >Cannot read property 'setNativeProps' of undefined react ...
Coding example for the question Cannot read property 'setNativeProps' of undefined react-native-React Native.
Read more >Cannot read property 'setNativeProps' of undefined
Hi i try to add a error Field when i do a setState i get. Cannot read property 'setNativeProps' of undefined on BuiltTextField....
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 Free
Top 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
I haven’t run into this issue before but will happily reopen this issue if it is still around!
(Definitely don’t mean to be dismissive of the issue, and apologize for not seeing it sooner – just that a lot changes still in one month so it’s quite possible that this is already fixed)
I have got into this problem when I was using Animated api and what I found was if the component did not mount, you will get this issue. So it does sound a little bit cryptic.