I've had a corrupted keystore before. What I do is place a version in my package name, like com.example.myapp.v1. So if I lose or get a corrupted key, I can just change my package name to com.example.myapp.v2. Changing the package name is important because you can't update an app with the same package name, but different sigs.
Most of my apps are prohibited from the Android Market, so I have an auto-update internally in my app. When the new signed version comes down, it installs just fine. Now there will be the old and the new versions installed on the device (different keys and different sigs). To prevent confusion to the user, I add the version to the label, so it would look like MyApp 1.0, MyApp 1.1. I guess in the case of the Android Market, you are pretty much screwed. On Thu, Jul 8, 2010 at 9:09 PM, kanatacrude <[email protected]> wrote: > Any ideas on the least painful way to somehow continue releasing new > versions to my users? I can't sign with the old keys anymore. Woe is > me. > > Any thoughts? > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- Shane Isbell (Founder of ZappMarket) http://apps.facebook.com/zappmarket/ -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
