Importing .keystore to Icenium

4 posts, 2 answers
  1. Answer
    Robin
    Robin avatar
    40 posts
    Member since:
    Jul 2012

    Posted 11 Jan 2014 Link to this post

    I wish to publish to Google Play an update for an app that I've previously published outside of Icenium. In order to upload the new APK it must be signed using the same certificate as the very first APK.

    For the first APK that I published I only have the Keystore file, named appname.keystore.

    When importing cryptographic identities to Icenium only .p12 files are accepted. 

    How do I go about it to import the certificate to Icenium so that I can correctly sign the update?

    Note: I did try using keytool to convert, but I don't get the same fingerprint. Is this because it's the wrong .keystore file, or because I'm entering different values for validity, organization etc.?
  2. Answer
    Robin
    Robin avatar
    40 posts
    Member since:
    Jul 2012

    Posted 11 Jan 2014 Link to this post

    Problem solved, I was using keytool with the wrong parameters. Here's the correct way to make the .keystore file into a .p12 for import in Icenium:

    keytool -importkeystore -srckeystore path/originalfile.keystore -destkeystore path/newfile.p12 -deststoretype PKCS12

    And that's it! 
  3. Durlabh
    Durlabh avatar
    1 posts
    Member since:
    Sep 2015

    Posted 25 Sep 2015 in reply to Robin Link to this post

    Do do you remove previous selected certificate? I accidentally added wrong certificate but now i am unable to remove it.
  4. Tsvetina
    Admin
    Tsvetina avatar
    1876 posts

    Posted 30 Sep 2015 Link to this post

    Hi Durlabh,

    Where are you trying to delete the certificate from? Deleting a certificate is allowed in all AppBuilder clients.

    Regards,
    Tsvetina
    Telerik
     

    Visit the Telerik Verified Plugins Marketplace and get the custom Cordova plugin you need, already tweaked to work seamlessly with AppBuilder.

     
Back to Top