Atul R

Hi @Louies89 From the readme > NOTE: setNativeExceptionHandler only works in bundled mode - it will show the red screen when applied to dev mode. If you are seeing red...

Does it not catch any errors ? I mean does it work without the isFatal check ? ``` const errorHandler = (e, isFatal) => { Alert.alert( 'Unexpected error occurred' );...

Can someone create a simple react native app repo with reproducible error ? So that we can take a look at it. @ManigandanRaamanathan @mstankov

@fatfatson Can you include all the changes in one pr and close the rest ?

For the userInfo loss. @fatfatson Can you raise a PR for the same ? raiseException is not meant to be used in a live project. Hence it will not be...

Hi @fatfatson Thank you for the PR. It looks good to me. But I don't believe that raise test native exception should be part of this module. The main reason...

I am not really sure if I get this right. Can you please give a link to a sample repo with the issue ?

"Uncaught Errors" are bubbled up. So setting an error handler on the root should catch them even if errors come from sub components. But if you are catching these errors...

Could you please raise a PR for this and we can take a look?

alright makes sense: How about we do it this way @Morriz and @ufolux ? ```js const consoleError = console.error; console.error = (...args) => { const error = args[1]; global.ErrorUtils.reportError(error); consoleError(...args);...