Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Version 9.0.1 crashes previously working code
See original GitHub issueI assume 9.0.0 would do the same. The error we get is el.querySelectorAll is not a function, but I’m not really sure of the cause beyond that.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Xcode 9.0.1 crash on App Store sub… - Apple Developer
I'm working on a Mac App and I'm trying to submit it for the first time to the App Store. Everytime I try...
Read more >VTK-9.0.1 crashes on code that was fine with VTK-8.2 (#17996)
Hi there, some code regarding polydata filtering worked perfectly fine with VTK-8.2 but since the update to VTK-9.0.1 vtk crashes in some ...
Read more >Notes 9.0.1 frequent crashes caused by embedded Sametime ...
The client crashes, the nsd information comes up and after a few seconds the client restarts and presents the login window. I tried...
Read more >LO88798: NOTES 9.0.1 FP5 IF2 / IF3 CRASH WHEN ... - IBM
Error description. The customer is making use of Lotus Notes 9.0. 1 FP5 IF2 / 3 with ST Embedded on Windows 10 Enterprise...
Read more >SceneBuilder-9.0.1 unusable due to crashes on OSX · Issue #167 ...
Originally reported by: Anonymous Issue The dmg version of SceneBuilder-9.0.1 from gluonhq crashes often on OSX. Cause This is due to the bundled...
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
🎉
Interesting! Thanks for digging into it. I’m surprised this only surfaced as of 9.0.0, unless the use of
ReactDOM.findDOMNode(what-react-onclickoutside-gives-you)was somehow masking this issue. Actually, I guess it may have been finding that component node for you, and now without the use of this API, you need to correctly pass it in.My pleasure! 😄