Question about app signing and updating

Getting Started Newbie Questions
#1

hi - on the Google side: I lost the keystore for one of my Google play apps a couple years ago and was unable to update my app. I ended up releasing it again with a slightly new name, which was annoying.

On the Apple side: is there are similar potential way of screwing-up that I should be aware of? Apple seems to make it easier by giving us a place to store and access our certs and profiles, etc., but in terms of app signing, what analagous mistake would I have to make on the Apple side such that I would not be able to update an app? Thanks.

#2

Apple is a bit safer because they make you generate a new certificate every year, which then requires you to generate new provisioning profiles. They also don’t bind your online product to the signing of the original upload. 

Rob

#3

ok thanks.

Most everyone online says that once you’ve lost an Android keystore you’re hooped in terms of every updating that app. However from the developer console you can email for support, and they give you some problem types to choose from, one of which is “lost keystore”. I haven’t heard back from them yet but anything interesting happens I’ll post about it.

#4

Apple is a bit safer because they make you generate a new certificate every year, which then requires you to generate new provisioning profiles. They also don’t bind your online product to the signing of the original upload. 

Rob

#5

ok thanks.

Most everyone online says that once you’ve lost an Android keystore you’re hooped in terms of every updating that app. However from the developer console you can email for support, and they give you some problem types to choose from, one of which is “lost keystore”. I haven’t heard back from them yet but anything interesting happens I’ll post about it.