Required certificate specifications for the custom debug KeyStore of Eclipse ADT

The recent launch of the In-app billing IAB built-in billing API for Google Play found that a more annoying problem was that the application had to be formally signed while testing, and that the default Eclipse ADT Debug run was using a temporary generated debug certificate. The default is C:\Users\XXX\. Android\debug. KeyStore.

So every time you debug built-in billing you have to use ADT's export signed application package to play with formally signed packages, more cumbersome. ADT was later found to allow custom debugging with a certificate, in Window->preferences->android->build->custom debug keystore here, after trying to select the official certificate after the prompt: " Keystore is tampered with, or password is incorrect ", as shown in:


In fact, this interface does not provide input keystore password, choose Alias and so on, so it is very strange, looked at the official documents found that even the custom debug certificate, you also need to guarantee the same password as the default certificate, alias aliases and alias password.

The default certificate information that is mentioned in the documentation is as follows:

Keystore Name: "Debug. KeyStore "
Keystore Password: "android"
Key alias: "Androiddebugkey"
Key Password: "Android"
CN: "Cn=android debug,o=android,c=us"

By following this rule, you can use a custom debug certificate. But think about the feeling that this function is very chicken, I hope the future version of ADT will improve it.

Required certificate specifications for the custom debug KeyStore of Eclipse ADT