Configure Eclipse to use signed keystore
I was able to to use my Google Play release keystore as my custom debug keystore to help with debugging in-app purchase functionality. The same could no doubt be applied to debugging Google Maps stuff as well.
As Devunwired mentioned, there are caveats. But my solution was this:
- Copy your release key somewhere.
- Change the keystore password/key password and key alias following the instructions here (also, following Devunwired's recommendations to make it look like a debug keystore).
- Change Eclipse's Preferences > Android > Build > Custom keystore setting to the path of the copy made in step 1.
- Done!
How to set a custom keystore for debugging in eclipse for android
I had the same issue and here are the steps to properly create a custom keystore that can be used for debugging in Eclipse:
Basically what you should do is that change both storepasswd
and keypasswd
for the alias androiddebugkey
to "android".
Here are the commands:
keytool -changealias -keystore mykeystore.keystore -alias [old alias] -destalias androiddebugkey
keytool -keypasswd -keystore mykeystore.keystore -alias androiddebugkey
keytool -storepasswd -keystore mykeystore.keystore
If you don't know your old alias, look it up using
keytool -list -v -keystore mykeystore.keystore
in Command prompt not able to enter the password
Importing SSL Certificate into Eclipse
Probably you want to import a "fake" SSL cert in JRE's trustcacerts for avoiding not-a-valid-certificate issues. Isn't it?
As Jon said, you can do the job with keytool:
keytool
-import
-alias <provide_an_alias>
-file <certificate_file>
-keystore <your_path_to_jre>/lib/security/cacerts
Use "changeit" as the default password when asked (thanks Brian Clozel). Ensure to use this runtime at your server or launch configuration.
Problem running my signed, release keystore in Eclipse
In Windows->Preferences->Android->Build you can just change your DEBUG KEYSTORE. The Keystore you specify there, is not for signing an app for release, but just for debugging.
Like the default debug keystore, the custom debug keystore needs to have the following:
Keystore password: "android"
Key alias: "androiddebugkey"
Key password: "android"
Except for the name of the keystore itself, information about the organizational units and the key behind the alias, all data have to be same as the default debug keystore
How to set up Java to use user specific certificates for Eclipse?
Use a user-specific configuration.
Setting the private configuration area location
The default location for a private configuration area is:
user-home-dir/.eclipse/<product-id>_<product-version>/configuration
The user home dir is determined by the user.home Java system property. The product id and version are obtained from the product marker file .eclipseproduct under the Eclipse install.
How to create a signed Android application?
Follow this tutorial about Build Android application package file (APK) using Eclipse IDE and Android Developer Tools (ADT) Plugin. In here describe how to Create new keystore.
Related Topics
Android Multiple Screen Sizes with Same Density
Custom Global Application Class Breaks with "Android.App.Application Cannot Be Cast To"
Cordova Platform Add Android Not Working While Listing Android Targets
Live Character Count for Edittext
How to Set Toolbar Text and Back Arrow Color
Android On-Screen Keyboard Auto Popping Up
Connectivity_Action Intent Received Twice When Wifi Connected
Android Task Affinity Explanation
Multiple Table SQLite Db Adapter(S) in Android
How to Disable Crashlytics During Development
How to Run (Not Only Install) an Android Application Using .Apk File
Can't Put Double Sharedpreferences
How to Add "Android Design Support Library" to Eclipse with Adt-Plugin