after finishing my android application development i used the command showing below to get private key, but it shows some errors such as "The Keystore was tampered with or password was in correct"
$ keytool -genkey -v -keystore DEBUG.keystore
-alias alias_name -keyalg RSA -keysize 2048 -validity 10000
Is my problem with DEBUG.keystore?? Should i need to generate another keystore for public release??
Yes, you should definitely generate another key for public release (and keep it in a save place for future updates).
See http://developer.android.com/guide/publishing/app-signing.html#releasemode for details.
EDIT:
If you'r using Eclipse, use the ADT Plugin for Android to create your keyfiles and sign your application.
Related
Followed some guides but I cannot get it quite right. I will show you the process below that does not make it quite work.
First of all I started off by acquiring an API-key on google console and i put that into my project.
I acquired the sha 1 by typing this into the terminal:
keytool -list -v -keystore ~/.local/share/Xamarin/Mono\ for\ Android/debug.keystore -alias androiddebugkey -storepass android -keypass android
The map now runs smoothly and fine in my xamarin project when I run it on my device.
Then when I try to upload the project I create a keystore named: "myproject.keystore" and I give it the Alias and password: "myproject" as well.
Just like this:
$ keytool -genkey -v -keystore myproject.keystore -alias myproject -keyalg RSA -keysize 2048 -validity 10000
When I now upload the app to google play and it gets accepted I cannot see the map.
Try comparing your project settings between DEBUG and RELEASE to find a difference. Or check for any hard coded API keys or anything that that would be different between the two environments.
Edit:
So after your myproject.keystore is created, you need to extract the SHA-1 from that keystore and add that to the Credential list in Google.
So if you created your myproject.keystore in ~/Users/Someone/Desktop/, then you would extract the keystore the same way you did with the DEBUG version:
keytool -list -v -keystore ~/Users/Someone/Desktop/myproject.keystore
That should give you the second SHA-1 that you need to add to the Google site.
hi its my first android project, i build my unsinged apk, i have no prior experience with certificates, follow tutorials from android developer page for signing my app, create a keystore using cmd keytool -genkey -v -keystore c:\users\anita\my-release-key.keystore
-alias alias_name -keyalg RSA -keysize 2048 -validity 10000
tried to signed app jarsigner -verbose -keystore my-release-key.keystore flying_birda.apk alias_name
jarsigner: certificate chain not found for (my alias_name). alias_name must reference a valid keystore key a private key and corresponding public key certificate chain.
i see a same problem
Certificate chain not found
is it a problem that my keystore have only a public key? if yes
then anyone can help me ho to make a complete key entry with a private key.
i am working it from last 2 days
but did not solve my problem.
how can I sign it properly outside eclipse or android studio?
any help will be greatly appreciated
Use haibision apk signer from github
I am quite new to android, this question maybe quite simple. But i do need your help. I am preparing to submit a update to google play now. When i export the android application, there is a keystore selection dialog. But i don't have the keystore. The project was developed by another company before. Now we only have the source code and the google play developer account. After reading the Signing Your Applications, i know i need to generate one. But there is still something i am not sure about this.
The keystore generate command as below:
$ keytool -genkey -v -keystore my-release-key.keystore -alias alias_name -keyalg RSA -keysize 2048 -validity 10000
This is a self-signed certificate. Is this sufficient for me to submit the update? Or need me to generate another one ? if so, then how to do that?
Any suggestion would be much appreciated.
For creating your own Keystore go to C:\Program Files\Java\jdk1.6.0\bin and execute below command
C:\Program Files\Java\jdk1.6.0\bin>keytool -genkey -v -keystore app.keystore -alias app -keyalg RSA -keysize 2048 -validity 300000
It'll created your app.keystore in C:\Program Files\Java\jdk1.6.0\bin directory and by using this keystore you can sign you application. You must keep this keystore safe because of your app next update.
Update: command for generate SHA-1 from your app.keystore
D:>keytool -v -list -alias app -keystore "D:app.keystore" -storepass app -keypass app
Right click to the project --> select Android tools -->Export signed Application package
this bring you to window "Export Android Application"
Complete the rest. this will give you signed apk as well as keystore
You can take help from this link too :https://www.youtube.com/watch?v=IYhJp-jqJyM
You'll need the original keystore, otherwise you won't be able to update the application on the Play Store. Ask the previous developer to give the one he used to sign the application, then save it in the safest place you can think of.
I'm just trying to test an android application using Robotium. The issue I have is that I don't manage to re-sign the application in order to start a test project in Eclipse.
I've followed the tutorial from http://code.google.com/p/robotium/wiki/RobotiumForAPKFiles but with no success.
I've generated a .keystore file:
keytool -genkey -v -keystore myCertificate1.keystore -alias myKey1 -keyalg RSA -keysize 2048 -validity 20000
Running the jarsigner command:
jarsigner -verbose -keystore Certificate1.keystore path\appname.apk Key1
And I've got an error:
Certificate chain not found for: Key1. Key1 must reference a valid KeyStore key entry containing a private key and corresponding public key certificate chain.
Could anyone point me in any direction ?
You're giving your new key an alias "myKey1", but then you're trying to sign with "Key1" which (I presume) either does not exist or at the least reference the wrong key.
I am upgrading Android application that was previously uploaded to the market.
The algorithm is as follows:
Using Eclipse Android tools I export unsigned application package
Then, I am using the same script as at the 1st uploading:
keytool -genkey -v -keystore almeesoft.keystore -alias almeesoft -keyalg RSA -validity 10000
The script asks for the passcode.
Honestly, I do not remember the passcode that I used the 1st time, so I guess
The application is starting uploading
However, at the and I am getting the message
“The apk is not properly signed”
You must sign the apk with the same private key you used when you first uploaded it. If you do not remember the password then you are out of luck. You will not be able to ever update this application. You will need to upload this as a different application with a unique package name.
You are at big loss if you have forgot your password, signing a apk with different keystore will result in different application on android market.
read this
I was incorrect blaming the problem on the forgotten password. There are 2 scripts one needs to run at the first uploading
1.
keytool -genkey -v -keystore .keystore -alias -keyalg RSA -validity 10000 -keypass -storepass
2.
jarsigner -verbose -keystore .keystore .apk -keypass -storepass
The generated file .keystore should be saved.
On the 2nd uploading (updating) only the 2nd (!) script should be run using the same *.keystore file.