The first step:
Android generates its own certificate:
Under the bin directory of the JRE, run the Keytool command:
CD C:\Program Files\java\jre1.8.0_91\bin
Keytool-genkey-alias myappname-keyalg rsa-validity 10000-keystore C:\myappname.keystore
Then view the signature information:
To view signature information:
Keytool-list-v-keystore C:\myappname.keystore
You can see the MD5 information:
Certificate Fingerprints:
md5:81:f4:5d:9e:fd:4a:c9:ac:4b:c8:a7:8a:60:b7:bd:7g
When you go to the public platform to apply for mobile applications, you will be asked to fill out the application signature, this signature is actually this MD5 value, remove the middle colon, and become lowercase values:
81f45d9efd4ac9ac4bc8a78a60b7bd7g
Second step: , &NB Sp , &NB Sp Figure 1 Figure 1 Annotations 1 and 2 are in the development platform, the account log in to see. &NBS P , &NB Sp , &NB Sp Figure 2 Figure 2 3 is the same as the 2 in Figure 1, otherwise the payment will not wake up error. Figure 2 in 4 is the first step to generate the Myappname.keystore, click on the following browse to find this file just fine. In the first step, the application signature is generated in Figure 1, which identifies 1, which is the 81f45d9efd4ac9ac4bc8a78a60b7bd7g in this article. If there are multiple tests that are not the same myappname.keYstore want to get its signature quickly, here's a gadget for Android to get sign: The Https://pan.baidu.com/s/1qZVmuSW 3 can quickly get to signs. OK, I don't know the message, I went to bed. It's exhausting. Almost forgot to say the most important point, if all the above two steps to finish or can not pay, the server returned 100 or 1 then do not do anything at this time. It's good to have a test simulator, or a phone reboot, because there's a big hole in the cache. Remember, remember.
Hbuilder pack Android apk won't pay for problem resolution