I published an App a while back and would like to make updates to it. I've saved my password and Alias when i originally created the App but when i try export the App using the "Android Tools/Export Signed Application" option using Eclipse it prompts me for an existing Keystore. The only Keystore i can find is a debug.keystore in my .android folder under C:\Users\Username. I know you cant publish Apps on the Marketplace using the debug keystore. Does this mean i need to generate a new one from scratch using the existing Alias and password?
If so, is there an option in eclipse to do this??
You need the same key. If you really lost it, unfortunately you'll have to republish that app under a different name/key. If you use the wizard in ADT, it'll prompt you to generate a new key (or hopefully find your old one in some directory that you didn't check).
You have to use the same key, and wont be able to publish to the same application without it.
You can generate new ones via:
Using File -> Export -> Export Android Application, then follow the steps can generate a new one.
Related
I have migrated an old project of mine from eclipse to android studio (Ubuntu) with some limited success.
I now want to create a new project in Android studio, dragging in classes and refactoring them as I go.
Then I will want to submit my new Android studio project to the app store as and upgrade to my old project using the correct signing key.
My question is what do I have to keep the same in the new project as the old project so that I can do this?
Keep the following unchanged:
Your keystore file, alias name and password.
Your app's package name.
Don't forget to update your version code to the newer one.
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.
If I got this right, you just need to compile with the same key from your keystore, at export time. Of course you need to increase the version number in your manifest before uploading it, just like a regular update.
If you need more information, about how to sign an app with android studio look at the google developer guide
I'm developing an android project signing my app (while developing) with the debug.keystore ... Now I need to use the "real" production keystore (the one which I use when I upload my apk to the play store), while developing to test some in app purchases things.
So it would be great to use the production keystore in eclipse to start the app on my device, so I could use the eclipse debugger etc.
After finishing this testing I want to switch back to the debug.keystore .
So I tried to replace the debug.keystore file in the .android folder, but then I get the error:
Keystore was tampered with, or password was incorrect
since I have not entered the password yet. Where do I enter the password in eclipse (juno)?
Or is there better way (in a wizzard for example) in eclipse, without replacing the debug.keystore file directly, to specify the current keystore that should be used when launching my android application from eclipse run button?
Change the password to default password i.e. android.
here is the SO link . how to Change the Keystore password
I would like to just enter the password in eclipse for the release keystore (like in the export dialog).
Since there is no dialog & I don't want to mess with eclipse internal configuration I use a custom keystore as a work-around.
Read this answer for how to use your release keystore for debugging
If you have taken the backup of the debug.keystore and replaced it then it should not be a issue in replacing it back, However you can specify the debug.keystore from
Eclipse tool bar > Windows> Preference> Android> Build> Custom Keystore.
Also if you want the Keystore to be recreated simply delete it, eclipse will recreated on next run.
If you specify a custom keystore, you have to make sure that the entries are what the eclipse environment expects. Maybe they're not lining up with those requirements? Check out the docs
specifically the Signing in Debug Mode section for details
If i use the .apk file that is in the bin directory in the project in the workspace instead of generating the .apk by exporting the project does it make difference?
The apk file in the bin is signed using the debug key, which loses the benefit of signing your App. Your App should be signed using your own key (which is specified when you export the project) which kind of uniquely identify your Apps and protects (or tries to protect) your Apps from having someone alter your App and republish it. Also, when you upload an update for your App, it must be signed with the same key as the original App, so make sure to keep this key safe.
You can use the apk from the bin folder while debugging, but when publishing the app, you must export a signed apk, or sign the one from the bin folder manually.
However, an easier method would be to directly debug on a hardware device from eclipse, as this gives you access to various tools like the adb and LogCat, See this link for details.
I was currently developing Android applications on a windows machine and signing with a "production.keystore" which I originally created on the windows machine. Now that I have migrated on Mac OS,can i use the old "production.keystore" or should I regenerate a new one? Will I still be able to sign the apk and release update on Android Market?
Many thanks
Yes you can still use that keystore. It's a universal format, as long as you keep that file and have a android SDK on that machine you can use it to sign your apk, independant of the platform you're using. (The android sdk tools will take care of that).
Updates of your application are only possible if you sign with the same you used for initial publishing. So no, you should not generate new key. Use the existing one and keep it safe from harm - should you lose it, you will not be able to update your application anymore.
I've been through this when moving from Win to linux. I was able to just copy the original keystore file over to your new machine and use that to continue to sign stuff. Eclipse/ADT will prompt you for a keytstore to use when you select Export Signed.
If you sign with a new keystore and try to upload the apk as an update to an existing app on Market it wont allow it.
I have written a little program, by default, it is signed with debug certificate.
I checked the documentation at Android developer site, I don't know how to get the certificate and key, could someone advice me?
Right click your project:
Android Tools -> Export Signed Application Package
Give the project name which you want to sign. Click next.
If you want to create a new keystore, select "Create New Keystore".
Give the location where to save it. The name of the keystore should end with .keystore and give a password for it. Click next.
Give the details and click finish.
That's simple: within the ADT plugin you can extract signed apk just from the IDE. It will ask you for creating a keystore and a key in it. Remember to backup the keystore because it is necessary to upload an update to the market.
See the section in dev guide.