Fix Android parameters ordering

The current implementation raises "cannot have non-function argument after a function arg"
as of RN v0.48+.

This patch fixes this issue inverting the order of the arguments in the native implementation.
Proper checks are in place to make this change backward compatible and detect the previous API usage,
switching the parameters as needed.

Author: lexor90

android/src/main/java/com/masteratul/exceptionhandler/ReactNativeExceptionHandlerModule.java

@@ -28,7 +28,7 @@ public String getName() {
 
 
   @ReactMethod
-  public void setHandlerforNativeException(Callback customHandler, final boolean forceToQuit){
+  public void setHandlerforNativeException(final boolean forceToQuit, Callback customHandler){
       callbackHolder = customHandler;
 
       Thread.setDefaultUncaughtExceptionHandler(new Thread.UncaughtExceptionHandler() {

index.js

@@ -17,15 +17,28 @@ export const setJSExceptionHandler = (customHandler = noop, allowedInDevMode = f
 
 export const getJSExceptionHandler = () => global.ErrorUtils.getGlobalHandler();
 
-export const setNativeExceptionHandler = (customErrorHandler = noop, forceApplicationToQuit = true) => {
+export const setNativeExceptionHandler = (forceApplicationToQuit = true, customErrorHandler = noop) => {
+  var handler = customErrorHandler;
+
+  // backward compatible API
+  if (typeof forceApplicationToQuit === 'function') {
+    handler = forceApplicationToQuit;
+  }
+
+  if (typeof customErrorHandler === 'boolean') {
+    forceApplicationToQuit = customErrorHandler;
+  }
+
+  customErrorHandler = handler;
+
   if (typeof customErrorHandler !== 'function') {
     customErrorHandler = noop;
   }
 
   if (Platform.OS === 'ios') {
     ReactNativeExceptionHandler.setHandlerforNativeException(customErrorHandler);
   } else {
-    ReactNativeExceptionHandler.setHandlerforNativeException(customErrorHandler, forceApplicationToQuit);
+    ReactNativeExceptionHandler.setHandlerforNativeException(forceApplicationToQuit, customErrorHandler);
   }
 };