Hi!
One year ago I start develop my application.
As I read in AIR manuals I need to use certificate for Signing. I've bought it for one year.
Few days ago this certificate become expired and I've renew it.
I build new version of my APK with few changes and new certificate, but when I try to instal ot on Android device it shows message "Package with that name and different signature already installed".
I know that it is way to make this update is like "make new app name" OR "unintall old application and instal new version". But I can't realize it cause few thousands of user involved.
I've found this solution http://help.adobe.com/en_US/air/build/WS13ACB483-1711-43c0-9049-0A7251 630A7D.html It works OK for *.air files, but as I know it can't be used for *.apk
Then I was surprised: When I try to build *.exe with expired certificate, sdk shows message that it was expired. But when I try to build *.apk with my old certificate (which was expired one week ago) IT WAS BUILDED OK! And then it was installed OK I don't know how it possible.
Then I try to use self-signed certificates for making *.apk with new appname. And there is no warnings when apk with self-signed certificate installed.
So, there is a few questions:
1) Are certificate migration available for apk?
2) If android have no notifications about certificate type, then is it my mistake to use paid certificate? Cause for publishing to market i need only self-signed certificate. We have no plans to publish it on market, then i don't heard about this condition before.
3) Why my *.apk builded OK with expired certificate? How long will it continues?
Message was edited by: Selirion