Android studio certificate debug

Signing Your Applications

In this document

See also

Android requires that all apps be digitally signed with a certificate before they can be installed. Android uses this certificate to identify the author of an app, and the certificate does not need to be signed by a certificate authority. Android apps often use self-signed certificates. The app developer holds the certificate’s private key.

Signing Overview

You can sign an app in debug or release mode. You sign your app in debug mode during development and in release mode when you are ready to distribute your app. The Android SDK generates a certificate to sign apps in debug mode. To sign apps in release mode, you need to generate your own certificate.

Signing in Debug Mode

In debug mode, you sign your app with a debug certificate generated by the Android SDK tools. This certificate has a private key with a known password, so you can run and debug your app without typing the password every time you make a change to your project.

Android Studio signs your app in debug mode automatically when you run or debug your project from the IDE.

You can run and debug an app signed in debug mode on the emulator and on devices connected to your development manchine through USB, but you cannot distribute an app signed in debug mode.

By default, the debug configuration uses a debug keystore, with a known password and a default key with a known password. The debug keystore is located in $HOME/.android/debug.keystore, and is created if not present. The debug build type is set to use this debug SigningConfig automatically.

For more information about how to build and run apps in debug mode, see Building and Running.

Signing in Release Mode

In release mode, you sign your app with your own certificate:

1. Create a keystore. A keystore is a binary file that contains a set of private keys. You must keep your keystore in a safe and secure place.
2. Create a private key. A private key represents the entity to be identified with the app, such as a person or a company.

Add the signing configuration to the build file for the app module:

Invoke the assembleRelease build task from Android Studio.

The package in app/build/apk/app-release.apk is now signed with your release key.

Note: Including the passwords for your release key and keystore inside the build file is not a good security practice. Alternatively, you can configure the build file to obtain these passwords from environment variables or have the build process prompt you for these passwords.

To obtain these passwords from environment variables:

To have the build process prompt you for these passwords if you are invoking the build from the command line:

After you complete this process, you can distribute your app and publish it on Google Play.

Warning: Keep your keystore and private key in a safe and secure place, and ensure that you have secure backups of them. If you publish an app to Google Play and then lose the key with which you signed your app, you will not be able to publish any updates to your app, since you must always sign all versions of your app with the same key.

The rest of this document provides detailed instructions about how to generate a private key and sign your apps in release mode with Android Studio.

Signing Android Wear Apps

When publishing Android Wear apps, you package the wearable app inside of a handheld app, because users cannot browse and install apps directly on the wearable. Both apps must be signed. For more information on packaging and signing Android Wear apps, see Packaging Wearable Apps.

Signing Your App in Android Studio

To sign your app in release mode in Android Studio, follow these steps:

On the menu bar, click Build >Generate Signed APK.

On the Generate Signed APK Wizard window, click Create new to create a new keystore.

If you already have a keystore, go to step 4.

On the New Key Store window, provide the required information as shown in figure 1.

Your key should be valid for at least 25 years, so you can sign app updates with the same key through the lifespan of your app.

Figure 1. Create a new keystore in Android Studio.

On the Generate Signed APK Wizard window, select a keystore, a private key, and enter the passwords for both. Then click Next.

Figure 2. Select a private key in Android Studio.

On the next window, select a destination for the signed APK and click Finish.

Figure 3. Generate a signed APK in Android Studio.

Automatically Signing Your App

In Android Studio, you can configure your project to sign your release APK automatically during the build process:

1. On the project browser, right click on your app and select Open Module Settings.
2. On the Project Structure window, select your app’s module under Modules.
3. Click on the Signing tab.

Select your keystore file, enter a name for this signing configuration (as you may create more than one), and enter the required information.

Figure 4. Create a signing configuration in Android Studio.

Under Signing Config, select the signing configuration you just created.

Figure 5. Select a signing configuration in Android Studio.

You can also specify your signing settings in Gradle configuration files. For more information, see Configuring Gradle Builds.

Signing Considerations

You should sign all of your apps with the same certificate throughout the expected lifespan of your applications. There are several reasons why you should do so:

• App upgrade: When the system is installing an update to an app, it compares the certificate(s) in the new version with those in the existing version. The system allows the update if the certificates match. If you sign the new version with a different certificate, you must assign a different package name to the application—in this case, the user installs the new version as a completely new application.
• App modularity: Android allows apps signed by the same certificate to run in the same process, if the applications so requests, so that the system treats them as a single application. In this way you can deploy your app in modules, and users can update each of the modules independently.
• Code/data sharing through permissions: Android provides signature-based permissions enforcement, so that an app can expose functionality to another app that is signed with a specified certificate. By signing multiple apps with the same certificate and using signature-based permissions checks, your apps can share code and data in a secure manner.

If you plan to support upgrades for an app, ensure that your key has a validity period that exceeds the expected lifespan of that app. A validity period of 25 years or more is recommended. When your key’s validity period expires, users will no longer be able to seamlessly upgrade to new versions of your application.

If you plan to publish your apps on Google Play, the key you use to sign these apps must have a validity period ending after 22 October 2033. Google Play enforces this requirement to ensure that users can seamlessly upgrade apps when new versions are available.

Securing Your Private Key

Maintaining the security of your private key is of critical importance, both to you and to the user. If you allow someone to use your key, or if you leave your keystore and passwords in an unsecured location such that a third-party could find and use them, your authoring identity and the trust of the user are compromised.

If a third party should manage to take your key without your knowledge or permission, that person could sign and distribute apps that maliciously replace your authentic apps or corrupt them. Such a person could also sign and distribute apps under your identity that attack other apps or the system itself, or corrupt or steal user data.

Your private key is required for signing all future versions of your app. If you lose or misplace your key, you will not be able to publish updates to your existing appn. You cannot regenerate a previously generated key.

Your reputation as a developer entity depends on your securing your private key properly, at all times, until the key is expired. Here are some tips for keeping your key secure:

• Select strong passwords for the keystore and key.
• Do not give or lend anyone your private key, and do not let unauthorized persons know your keystore and key passwords.
• Keep the keystore file containing your private key in a safe, secure place.

In general, if you follow common-sense precautions when generating, using, and storing your key, it will remain secure.

Expiry of the Debug Certificate

The self-signed certificate used to sign your application in debug mode has an expiration date of 365 days from its creation date. When the certificate expires, you will get a build error.

To fix this problem, simply delete the debug.keystore file. The default storage location is in

/.android/ on OS X and Linux, in C:\Documents and Settings\ \.android\ on Windows XP, and in C:\Users\ \.android\ on Windows Vista and Windows 7.

The next time you build, the build tools will regenerate a new keystore and debug key.

Note that, if your development machine is using a non-Gregorian locale, the build tools may erroneously generate an already-expired debug certificate, so that you get an error when trying to compile your application. For workaround information, see the troubleshooting topic I can’t compile my app because the build tools generated an expired debug certificate.

Signing Your App Manually

You do not need Android Studio to sign your app. You can sign your app from the command line using standard tools from the Android SDK and the JDK. To sign an app in release mode from the command line:

Generate a private key using keytool . For example:

This example prompts you for passwords for the keystore and key, and to provide the Distinguished Name fields for your key. It then generates the keystore as a file called my-release-key.keystore . The keystore contains a single key, valid for 10000 days. The alias is a name that you will use later when signing your app.

Compile your app in release mode to obtain an unsigned APK.

Sign your app with your private key using jarsigner :

This example prompts you for passwords for the keystore and key. It then modifies the APK in-place to sign it. Note that you can sign an APK multiple times with different keys.

Verify that your APK is signed. For example:

Align the final APK package using zipalign .

zipalign ensures that all uncompressed data starts with a particular byte alignment relative to the start of the file, which reduces the amount of RAM consumed by an app.

Источник

How to obtain SHA1 Keys for debug and release — Android Studio [Mac]

Debug Key

Click on the Gradle tab on the right hand side of the Android Studio window.

Go to the Project root folder -> Tasks -> android -> signingReport

UPDATE: (Newer versions) In case you don’t find an android folder here, go to :app instead of root, navigate to Tasks>android and you’ll find signingReport.

Double click on signingReport, this will build and post the SHA1 in the bottom view.

Release

Method 1

In Android Studio, go to Build menu -> Generate Signed Bundle / APK

Select your keystore and key alias.

Copy the key store path and the key alias.

Here, the path is /Users/technofreek/Documents/testkeystore

and the alias is key0.

Open terminal and type the command

keytool -list -v -keystore -alias

For this example, here’s the command

keytool -list -v -keystore /Users/technofreek/Documents/testkeystore -alias key0

This will print your SHA1

Method 2

If you have enabled App Signing for your app in your Google Play Developer Console, by uploading your signing certificate, then just go to your developer console and select your app.

Select Release Management -> App Signing, and you’ll see you release SHA1.

Источник

How To Generate Certificate Fingerprint SHA-1 Using Android Studio

What is SHA-1?

Secure Hash Algorithm 1 or SHA-1 hash value is a unique representation of a certificate. Typically represented as a hexadecimal number with 40 digits long. This fingerprint value is requested by API providers like Google, Facebook along with package name of the app. They use SHA-1 fingerprint for registering the app to use their services securely.

Since it is a short representation of the developer certificate, it has become an important factor in establishing secure connection between app and service end points.

Today most of the apps depend on third party services and in future also this trend will continue. So i think this tutorial is relevant and will be helpful for Android developers in generating SHA1 fingerprint value.

Another reason is to write this tutorial is, many developers are using command-line tool like keytool for generating SHA1 fingerprint but if you are using Android Studio IDE, then you don’t have to use another tools because it is very simple in Android Studio to generate singing fingerprints.

Gradle is the build system used for Android development in Android studio IDE. Gradle is rich collection of tasks for various purposes. A gradle task named signingReport is responsible for generating fingerprint for the application.

Running the signingReport task against a particular build variant (debug, release) it will generate SHA-1 fingerprint value. SHA-1 fingerprint value will be different for each build variant. i.e, SHA-1 value of debug will be different from SHA-1 value of release build.

singingReport task will generate the following fingerprints,

Note: Best standard out of the above list is, SHA-256

How To Generate SHA-1 Fingerprint

Certificate fingerprints can be generated for any build variants like debug, release. Here i explain simple and secure way of generating fingerprint values which involves following 3 processes,

• Create keystore Properties
• Load keystore To Gradle
• Execute Gradle Task

[Optional] Generate Fingerprints For Release

If you only want SHA1 fingerprint value for debug build variant then you can skip this section to Step 1.

By default the gradle task will not generate fingerprints for release build variant. In most places you will only find how to generated certificate fingerprints for debug build variant but if you published your app in Google Play Store then the live version will be a release build. In this case you need to generate certificate fingerprints for release build variant too.

I will explain how to generate SHA-1 fingerprints for release build variant as well

If you need fingerprints for release build variant also then you have to do 2 additional things before you jump into build.gradle file,

• Create a keystore file (file with .jks extension)
• Add signingConfigs for release

If you already generated signed build for your app then you can skip keystore file creating part and jump to Step 1 and start creating keystore properties.

Keystore file is needed for generating signed apk also. So even if we don’t want to generate a signed apk, generating a signed build would be a good idea to get a keystore file.

Below is the tutorial on how to create a signed apk.

Step 1. Create Keystore Properties

Create a file named keystore.properties in the root directory of your project.

Open the keystore.properties file and past the following content to it.

Replace the above dummy values with your string values.

storeFile variable holds the path to where .jks file to be saved. Better create a folder for keystore file and give the full path of the keystore file.

Step 2. Load KeyStore Properties To Gradle

Once keystore properties file created with your secret credentials, next step is to load the keystore properties to the gradle build configuration. This will give access to the gradle tasks to the keystore properties.

Follow the below instructions to load keystore properties,

In your module’s build.gradle file, add 3 line of code to load your keystore.properties file before the android <> block to load the keystore to gradle.

Next add keystore properties for release build variant also. To do this, copy paste the release tag into signingConfigs

If we miss release singingconfigs then Gradle task will not able to generate certificate fingerprints for release build variants.

Step 3. Execute Gradle Task

signingReport is the name of task that performs the generation of SHA1 fingerprint. In the latest version of Android Studio,

FYI here i am using Android Studio 4.2 for the explanation.

You can find Gradle tab at the right hand-side of the Android Studio IDE. Clicking on the tab will open up the below window.

Click on the Gradle icon (Elephant icon) in the above window. It will open up a sub window,

Type gradle task run command: gradlew singingReport

Enter the command will start execution of gradle task and generate SHA1, MD5, SHA-256 fingerprints.

Step 4. Find Generated Fingerprint

After executing the signingReport you have to open Run tab, which is not selected by default.

Copy the long string shown against SHA1. SHA1 keys are generated and displayed under each build variant i.e, debug, release. Please go to corresponding variant section as shown in the above screenshot.

If you have added sinigingConfigs for release then you will get release variant also in the above result else, release variant will not be available.

Thank you. Please comment here if you have any doubt.

Источник