You can find many ways on the internet to get the SHA1 fingerprint for Android but here we are going to see specifically for React Native. There are two ways to get the Debug Keystore SHA1 which are using the CLI or by using Android Studio. Obtaining SHA1 Fingerprint from Android Debug Keystore In this scenario, we will get stuck if we have to change the machine so to remove this problem we generate a Release Keystore (.jks) for each App that is transportable and we can update our application from the other machine too by using this Release Keystore. So according to that if we sign a Release APK with the debug Keystore we have to update the same application with the same Keystore in the future which is easy if you are working on the same machine for the lifetime but it is not practically possible. We will see how to generate both API key but first of all the question is why we need two Keystores?Īs we all know SHA1 is the unique signature that depends upon the Keystore and Debug Keystore is unique for each system and it is automatically maintained by the Android SDK. As it requires private information such as name, password, etc. Release KeystoreRelease Keystore has to be generated manually by the user for each application before release.Debug KeystoreDebug Keystore has generated automatically when the Android SDK is installed or run for the first time.In Android there are two types of keystores: