Thus, this command prompts you for the password of the keystore, the actual key, and the distinguished name fields for your key. This key uses key-size 2048, instead of default 1024 for security reason. You can change your_key_name with any name you want, as well as your_key_alias. Once you run the keytool utility, you’ll be prompted to type in a password. You can create one using the keytool in the terminal with the following command keytool -genkey -v -keystore your_key_name.keystore -alias your_key_alias -keyalg RSA -keysize 2048 -validity 10000 You will need a Java generated signing key which is a keystore file used to generate a React Native executable binary for Android. If everything compiles as expected you are good to go. That means, it is compiling and running successfully on the emulator or on an Android device Thus, open the Android project using Android Studio or run it from the command line. Using React Native CLIįirst of all, make sure your Android project is error free. There are two ways to generate a production-ready build for Android, so we are presenting both of them below.

We are documenting our learnings in this React Native tutorial, to help mobile developers ship their Android apps to production more quickly. In this tutorial, we are going to learn how to generate a React Native Release Build APK for Android, using both React Native CLI and Android Studio IDE.Īt Instamobile, we launched all of our React Native Templates to production (Google Play Store demos), so we are familiar with the process as well as the errors that might show up when generating a React Native Release Build APK for Android.

React Native developers are often in the situation of releasing their React Native apps to the Google Play Store so that Android users can download them.

Android studio gradle output