The keytool then prints the fingerprint to the terminal. The default password for theĭebug keystore is android. The keytool utility prompts you to enter a password for the keystore. alias androiddebugkey -keystore %USERPROFILE%\.android\debug.keystore alias androiddebugkey -keystore ~/.android/debug.keystore Windows keytool -list -v \ To get the debug certificate fingerprint: Mac/Linux keytool -list -v \ To get the release certificate fingerprint: keytool -list -v \ You should get both the release and debug certificate fingerprints. Open a terminal and run the keytool utility provided with Java to get the SHA-1 fingerprint of theĬertificate. Keytool or Gradle's Signing Report to get your SHA-1. If you're not using Play App Signing, follow the instructions below to use On the Release > Setup > App Integrity page. You to provide the SHA-1 of your signing certificate so we can create an OAuth2Ĭlient and API key for your app. I pieced these steps together from the information found here and here.Certain Google Play services (such as Google Sign-in and App Invites) require & new File(project.property("yourprojectname.properties")).exists()) section into the condition in which the props variable is assigned then try again. if(project.hasProperty("yourprojectname.properties") (example for Windows) yourprojectname.properties=c:\\Users\\\\signing\\yourprojectname.propertiesģ) Create yourprojectname.properties file in the location you specified in Step 2 with the following information: keystore=C:\\path\\to\\keystore\\yourapps.keystoreĤ) Modify your gradle.build file to point to yourprojectname.properties file to use the variables. The location for this file depends on your OS: /home//.gradle/ (Linux)Ģ) Add an entry pointing to yourprojectname.properties file. With this solution you get the control of using your own keystore and the magic of automation during debug and release builds.ġ) Create a gradle.properties (if you don't already have one). Yes you can go to File -> Project Structure and assign signing keystores and passwords in the Signing tab but that will put plaintext entries into your gradle.build file which means your secrets might be disclosed (especially in repository commits). This solution also gives you the ability to store your keys outside of the project directory as well as enjoy automation in the signing process. You can specify your own debug keystore if you wish.
0 kommentar(er)
