About Android Studio packaging release, and the acquisition of Android signatures

This feeling is very important, especially the signature acquisition, because the use of Baidu map, so feel this should be written in front, there is also need to sign

Let's start by saying how Android Studio is packaged:

Bo Master test built a packaging project

Look at the directory structure first, because it is not the same as eclipse, can be optional, it is best not to use the default directory structure

OK, let's see how to package it.

Where to put the signature file, account password, and alias

Here, the signature is best placed in the root of the project, a person developed, or not very confidential, and other according to the actual situation

The second option cannot be made because it is a new key.

The following drawings illustrate

No, the OK option is not clickable.

Click Create, the following interface will appear, English is not difficult, we can fill in according to the corresponding

Here the path is chosen according to the root directory above.

As it seems the default is JKS format, but Eclipse seems to be the default KeyStore format, but the encryption method is not the same, the other does not affect

After confirmation, return to the original interface will be automatically replenished

Here, for the sake of convenience, you can select record password

Here I want to highlight, the above is the location of the APK package storage, the second is the packaging method, the third blogger did not use

This is the default directory structure, you can control the first picture, you know where the directory structure, it will be loaded in as, and will not hide, if less good, if more of this will occupy a large part of the directory structure, so it is best not to choose this directory structure, then choose where?

In fact, as long ago for you to think of, and directory agencies have been built for you

Directly selected in the APK this can be, as for the packaging method we will follow the default, release can be, the following say why

Okay, OK, go ahead and see what happens.

Here there are two installation packages, direct English translation can be, one is signed unsigned, unsigned packaging is not allowed to use, and then that is, the above choice packaging method release, why not choose debug,debug Default unsigned, And some of the file image format check is relatively loose, there are some string.xml files or other XML file name check is not very strict, do not have to force compilation

In turn, look at the current directory structure

Because of the signature, and Bo Master recorded the password, packaging will be convenient later, to see as more than the EC strong place

Here is very full, clean,debug,release and so on, after the pack more words will know the benefits, now one, but relatively more convenient

Double-click Release, package, build successful package complete

below to see how to get the signature, Bo owner for convenience, the signature file is placed in the root directory

Here to enter the password, and no cursor display

All signature information can be found.

About Android Studio packaging release, and the acquisition of Android signatures