TypeError: Cannot read property 'createErrorBoundary' of undefined
See original GitHub issueFollowing the Bugsnag Docs to config the project and run got this error from:
const ErrorBoundary = Bugsnag.getPlugin('react').createErrorBoundary(React);
- react 16.11.0
- react-native 0.62.2
- @bugsnag/react-native 7.5.0
Issue Analytics
- State:
- Created 3 years ago
- Reactions:7
- Comments:23 (10 by maintainers)
Top Results From Across the Web
React ErrorBoundary doesn't catch "cannot read properties of ...
But if I wrap a problematic place in the component, it works properly. const page = webtexts[courseId].pages[pageFamilyId]; // Returns undefined ...
Read more >Cannot read property 'createErrorBoundary' of undefined
Following the Bugsnag Docs to config the project and run got this error from: const ErrorBoundary = Bugsnag.getPlugin('react').
Read more >React integration guide - JavaScript - Bugsnag docs
You can set the user information of an error report using the user configuration property when Bugsnag starts or via an onError callback....
Read more >Fix "Cannot read properties of undefined" error #shorts
Sometimes in Javascript you might have an array of objects like this and you to need to get some of the properties of...
Read more >can not read properties of undefined - YouTube
Your browser can't play this video. ... can not read properties of undefined - reading createElement error in react.
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
Can you please reference this in your documentation until this is released? I just spend 2-3 hours thinking I setup my app was wrong, meticulously looking at the docs, but it looks like this feature just doesn’t work at all with recent versions of react-native and bugsnag, even with the base case in the documentation.
Hey @adkenyon, we’re looking into a fix for this notifier side. But, in the meantime you can guard against this by checking whether the
getPlugin()
call returnsundefined
, and in these cases point your application to a no-opErrorBoundary
, for example:When running without the debugger, Bugsnag will continue as normal with the Bugsnag error boundary.