Hi there, hopefully someone is able to help me out of my crucial situation:
We are publishing an app in the market/play store since last year. Now, we have the serious show stopper that google play store doesn't let us upload the apk-file for the latest update. During the upload process in android developer console it states, that the certificate which was used to sign the app isn't valid until 22 October 2033. Our certificate which was used to sing the former versions is valid until October 2022. Referring to Android app signing strategies the certificate's validity should exceed the expected lifespan of the app, which is the case (10 years). The recommendation that a certificate should have a validity period of at least 25 years, did not sound as an obligation to us. The certificate validity never seemed to be a problem, when performing former app updates (last update January 2012). We assume that since google market switched to google play store, the recommendation turned into an obligation. This fact would chop the evolution process of our app, furthermore it would stop the lifespan immediately, because: - Developer console doesn't let us update the app file any longer, because current certificate is not valid until 22 October 2033. - Developer console doesn't let us update the app file any longer, because it doesn't accept a different certificate. - Developer console doesn't let us update the app file any longer, because it doesn't accept the apk file if it's signed with the current an a new certificate - Certificate's validity cannot be extended. Due to the fact that our customer's IT department is about to change some behavior of the eCommerce interfaces, the current app will stop working soon. For that reason we don't only have to update the app because to improve the functionality we also have to update the app because it stop working soon. Is there any way or workaround to find an acceptable strategy for handling the certificate problem? Does anyone know any individual way of migrating our current certificate to a new one with a longer validity period? Is there any enterprise support for android app incidents? The strategy to treat the current update as a brand new app (in order to be able to upload the apk) is not acceptable for our customer, because they would lose all current ratings & comments, furthermore people who already installed the app would not be notified about a new release. If it's not possible to find a solution for the certificate problem, is there a way to get in touch with the users who already installed the app. For example getting the emails of that users in order to inform them about a new release? We appreciate any help and fast response. -- 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
