Google Play Publishing vNext

4 posts, 0 answers
  1. Shawn
    Shawn avatar
    6 posts
    Member since:
    Sep 2012

    Posted 03 Feb 2014 Link to this post

    Our organization has an app published in Google Play.  We have a deployment team that takes care of the actual publishing so bear with me.  Publishing v1 went fine.  I provided them the Icenium instructions.  However, when we went to publish v2 we got a message that the .apk file must be built/signed with the same .p12 file as the original one.  The problem is I never created nor have knowledge of the .p12 file that was originally used since it was a different team that actually deployed it.  They also stated they don't have the .p12 file so I'm lost as to what .p12 file was used.  I originally provided them an .apk file for distribution to an internal app store for testing purposes (I kicked off a build in release mode and emailed the .apk file to them). Is it possible for that .apk to be submitted and approved in Google Play?  Does it use some generic .p12 file?  If so, how can I submit v2? 
  2. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 06 Feb 2014 Link to this post

    Hi Shawn,

    An already published app can only be updated in the Google Play store if signed with the same certificate used for the original publish of the app. In order to build an Android app in Icenium in Release mode, you create a certificate if none available or import an existing one. In either case, this certificate should be used for any future builds once you publish to the Play Store. I reviewed your account and noticed that there aren't any certificates in it, so you've either used a different account or you have deleted it despite the disturbing warning message we show when you try to delete it.

    In short, we cannot restore your certificate and Google Play Store does not have a fail safe for such case. You would have to create a new one and change the app's package name. Then create a new listing on Google Play, this time signed with the new keystore, unpublish the old listing and notify users that they will need to re-install the app via the new Google Play listing.

    Regards,
    Steve
    Telerik
    Icenium is now Telerik AppBuilder, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)
  3. Shawn
    Shawn avatar
    6 posts
    Member since:
    Sep 2012

    Posted 06 Feb 2014 in reply to Steve Link to this post

    Are the certificates stored in the cloud as part of the project?  Or do they remain local?  I was able to determine the name of the certificate used to sign the .apk and I don't know why I would have deleted it. Could they have been lost in any of the Icenium upgrades over the past 6 months?  I'll have to dig around my computer to try to find the certs.  I should have taken better care of the cert...
  4. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 07 Feb 2014 Link to this post

    Hello Shawn,

    They are stored in the cloud, so that they can be used on subsequent builds, but as mentioned in previous reply, your account does not have any. We have not deleted anything from our servers from the last 6 months.

    Regards,
    Steve
    Telerik
    Icenium is now Telerik AppBuilder, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)
Back to Top