nodeHandle expected to be non-null
See original GitHub issueError raised:
nodeHandle expected to be non-null
Upon calling goBack();
on the webview.
This is happening on our production app and we haven’t found a repro case yet. It does seem to occur only on iOS though.
We’re using RN version 0.59 (latest), rn webview version 5.10.0.
Any ideas what could be causing it?
Issue Analytics
- State:
- Created 4 years ago
- Comments:11
Top Results From Across the Web
React-Native-Webview: Expected nodeHandle to be not null
goBack() I get the exception of nodeHandle expected to be non-null . Here is my piece of code <View style={{ flex: 1 }}>...
Read more >nodeHandle expected to be non-null · Issue #908 - GitHub
I am experiencing this as well. I am using React Navigation for my app. In the initial load of the web view screen,...
Read more >React-Native-Webview: Expected nodeHandle to be not null
The reason for this problem may be that your component has been rendered for a certain condition at the beginning, but after the...
Read more >roscpp: node_handle.cpp Source File - ROS Documentation
77 NodeHandle::NodeHandle(const std::string& ns, const M_string& remappings) ... 162 // if callback_queue_ is nonnull, we are in a non-nullary constructor.
Read more >org.apache.xml.dtm.ref.DTMDefaultBase.error java code ...
Append a text node child that will be constructed from a string, * to the end of the document. ... Given a node...
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
Thanks for the reply! Can you be more specific maybe showing the before/after code?
Currently it looks like this for us:
ref={(webView: WebView): void => { this.webView = webView; }}
And the error is still happening, no global reference.
In my case, I had kept a global reference for the
ref
prop of the WebView. By removing that with a class level reference, the error was fixed.