Is the same API key can be worked on this my project in Android Studio?Įasiest ways ever: Update added for Android Studio V 2.2 in last step Is there a way to find the SHA-1 fingerprint from Android Studio like it was very easy in Eclipse? As I am newbie in Android Studio, what is the full process to find it?Īnother thing I want to add is that I have my Eclipse generates the SHA-1 fingerprint and previously I have my app registered on that fingerprint in Google developer console, and I worked on that app in Eclipse by that API key. keytool -list -v -keystore "%USERPROFILE%\.android\debug.keystore" -alias androiddebugkey -storepass android -keypass android It is saying that it is an illegal option. So I tried to run this in command line after setting my Java bin path from this link and unfortunately couldn't find my fingerprint. I have read from this link that:Īndroid Studio signs your app in debug mode automatically when you But in Android Studio I couldn't find out any option like this so that I could find easily the fingerprint. When I was using Eclipse it was right under Windows -> Preferences -> Android -> Build. So I need my SHA-1 fingerprint certificate number. I pieced these steps together from the information found here and here.I have shifted myself from Eclipse to Android Studio. & 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)
