React: Cannot read property 'getNativeNode' of null (ReactReconciler)
Hello everyone. I have a problem after updating React from v0.14.8 to the current latest v15.1.0.
Actually, I cannot even tell what exactly cause this problem. On some pages of my SPA everything works just fine, but during one specific action in my app, this error happens.
This problem appeared after React (and some dependent libraries) update
timzekid
All 7 comments
Thank you for reporting!
We also saw this error in production on a React Native app but couldn鈥檛 find a way to reproduce it.
Can you try slimming it down to a small case that reliably reproduces it, and share that case?
gaearon
on 24 Jun 2016
(Note: we probably won鈥檛 be able to fix it without a case reproducing it.)
gaearon
on 28 Jun 2016
Looks like I fixed it for my case. Obviously, I shouldn't been creating the issue in this repo, as in my case the problem was not in React itself, but in my absent-mindedness. But I'll share this case anyway. The problem appeared on a page with RadioButton Component from Material-UI lib. As I mentioned before, during a React update, I also updated some dependent libraries, including Material UI. In the new version of MUI a file structure has changed, so I had to change the way I import MUI components into my files. That's where the problem had it roots. I mistakenly imported RadioButton Component instead of RadioButtonGroup component (if you're familiar with MUI lib, then you know that the structure should be 'RadioButtonGroup > RadioButton', and in my case it was 'RadioButton > RadioButton', which is inappropriate). This led to the error on a screenshot, which, obviously, led to the error "Cannot read property 'getNativeNode' of null".
timzekid
on 29 Jun 2016
That鈥檚 super useful, thanks!
gaearon
on 30 Jun 2016
I think this still counts as "exception thrown during render": https://github.com/facebook/react/blob/6cc037bd0d49f1f55cbdd36fbfd395118c64d393/src/renderers/dom/shared/ReactDOMComponent.js#L156. :\
sophiebits
on 30 Jun 2016
Well, we now know that ReactDOMComponent.mountComponent throwing can lead to a null child in multichild. I wasn鈥檛 sure how to repro this before.
gaearon
on 30 Jun 2016
Closing because it seems like React got into an inconsistent state due to the user error above.
Still not very good but at least it's possible to fix in apps.
gaearon
on 27 Oct 2016
Related issues
tleunen
路
3Comments
Prinzhorn
路
3Comments
zpao
路
3Comments
zpao
路
3Comments
jmullo
路
3Comments
Most helpful comment
Looks like I fixed it for my case. Obviously, I shouldn't been creating the issue in this repo, as in my case the problem was not in React itself, but in my absent-mindedness. But I'll share this case anyway. The problem appeared on a page with RadioButton Component from Material-UI lib. As I mentioned before, during a React update, I also updated some dependent libraries, including Material UI. In the new version of MUI a file structure has changed, so I had to change the way I import MUI components into my files. That's where the problem had it roots. I mistakenly imported RadioButton Component instead of RadioButtonGroup component (if you're familiar with MUI lib, then you know that the structure should be 'RadioButtonGroup > RadioButton', and in my case it was 'RadioButton > RadioButton', which is inappropriate). This led to the error on a screenshot, which, obviously, led to the error "Cannot read property 'getNativeNode' of null".
