I got into a slightly annoying situation with Android keystore files. I currently have several different applications, each of which is signed with a different keystore file. Kind:
- AppName1.apk is signed with AppName1.keystore
- AppName2.apk is signed with AppName2.keystore
- AppName3.apk signed with AppName2.keystore
Each of the keystores contains different names and aliases for each application.
Now I find out that doing this is so little silly, and it would be better to use a single keystore file for all my applications. I'm going to publish a new application, so this time I'm trying to do it right.
My general question is: what can I do to make life easier in the future?
I read that I can rename one of them to the keystores and change the aliases, so theoretically can I sign my next application with one of the existing keystores? This will mean that at least 2 of my applications use the same keystore, and it will have a reasonable name.
EDIT: for reference, this is one of the lessons I read today:
http://blog.blundell-apps.com/tut-change-alias-passwords-of-your-android-keystore/
as well as this other answer:
Is it possible to change the alias of my key?
From my guide, I understand that I can safely rename a keystore file, change passwords and rename an alias without losing the ability to update an existing application. Can anyone confirm that this is true, or if there is a way to prove it?
, 3- , , ? . , , , , .
, .