I have an app that's been developed on two computers. The Keystore was created on one of the computers but I want to use that Keystore to export the signed APK on the other computer. I moved the Keystore file over with a flash drive and selected to use an existing Keystore in Eclipse. After entering the password I got the error below when I had to select the alias. It wouldn't let me select an alias so I couldn't continue with the exporting. Anyone know if Keystores can be created on one computer and used on another, or how to fix this problem?
Nevermind, I found the answer to my own question. Apparently the keystore file I transferred over was corrupt.
Related
I've been learning programming on Android Studio and already have an app about to publish. Some points are missing for trying to learn by myself and my question may sound silly.
3-4 months ago I generated my first signed apk. Since then as I developed my app, sometimes I generated apks to test my app. When I was generating signed apks keystore file (jks) path
was remembered and I quickly click forward button to generate signed apk. The location of my jks file was "C:\Users\Me\AndroidStudioProjects\MyApp\feature\build\outputs". After Android Studio update I can not generate signed apk with this key. Whatever I do, they all end with "No key with alias '....' found in keystore C:\Users\Me\Desktop\"
Keystore path is always seems as desktop. I can not change it. When generating apk I already select my existing keystore path but Android Studio always looks for keystore file on desktop.
Another problem is alias name mentioned in the error message is different my existing alias name. Android Studio looks wrong place and wrong alias name. So why is Android Studio acting like this? How can I generate a signed apk again?
My issue is that I have published an APK from my machine, and after that I have formated the machine. Now, I'm trying to create the sign APK from the same machine after formatting, but I am unable to do do.
I am using same keystore .jks file also I provide same .jks file and same alias name & password. I have also tried to do the same from other machines, but not able to do so.
I switched to a different computer (all opensuse linux with eclipse) and I am not succeeding in signing my updated app with the same key.
Advised by other posts on stack I :
tried to delete trusted.certs (but could not find this file)
looked for debug.keystore. There was one on my old computer. If I open this in export-> exclipse, he asks me for a password instead/or asks if it was tampered with of the "keystore not valid". Did not succeed in inputting the right password.
I could not find deault.keystore in ~/.android
I have a file that I think is my keystore, but I am not sure it is. Could somebody verify this? Here is the file: https://dl.dropboxusercontent.com/u/13564139/dorienhskey
When I try to export with this keystore, I get "Invalid keystore format". I have this file and thisfile.pub in my project directory. Perhaps this is not the keystore, but the key somehow? Would it be possible that I uploaded my app with the debug.keystore? As I can't find any other.
Should I look for some other file?
That doesn't look like a keystore. That looks like a certificate.
You cannot update your app with the debug keystore. You will need to use the keystore which you had used the first time.
How to find? Keep looking at other places.
Identify: If you open the file in UTF encoding, you should see some text, like your "Name", or "Organization Name", you might have given when you had created that keystore.
You could try open the debug.keystore and see what it looks like. Your keystore would be similar.
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
I am using Eclipse export for signing apk file (right click on the project, than Export...). Eclipse ask me for keystore and password. I am sure i put the same password and the same keystore like before, but it does not work: Eclipse is writing Keystore was tampered, or password is incorect.
I do not why i could sign my .apk before and now it does not work. Without signing my .apk with the same keystore it is impossible to upload upgrade to market :-(.
Thank you
If it says Keystore was tampered, or password is incorect, high chance that a wrong password was entered. Make sure you check for any caps in the password.
Secondly, make sure you use the same keystore for the same application you uploaded on the market.
One solution for you is if you still can't solve the problem, you will have to create another keystore and change the package name of your project.