You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Previously defined exception handlers are not executed anymore
476
+
477
+
A lot of frameworks (especiallyanalyticssdk's) implement global exception handlers. In order to keep these frameworks working while using react-native-exception-hanlder, you can pass a boolean value as third argument to `setNativeExceptionHandler(..., ..., true`) what will trigger the execution of the last global handler registered.
console.log('setJSExceptionHandler is called with wrong argument types.. first argument should be callback function and second argument is optional should be a boolean');
11
-
console.log('Not setting the JS handler .. please fix setJSExceptionHandler call');
console.log("setJSExceptionHandler is called with wrong argument types.. first argument should be callback function and second argument is optional should be a boolean");
10
+
console.log("Not setting the JS handler .. please fix setJSExceptionHandler call");
console.log('setNativeExceptionHandler is called with wrong argument types.. first argument should be callback function and second argument is optional should be a boolean');
28
-
console.log('Not setting the native handler .. please fix setNativeExceptionHandler call');
console.log("setNativeExceptionHandler is called with wrong argument types.. first argument should be callback function and second argument is optional should be a boolean");
27
+
console.log("Not setting the native handler .. please fix setNativeExceptionHandler call");
0 commit comments