Import p12 certificate null expiration date

4 posts, 0 answers
  1. Andrew
    Andrew avatar
    2 posts
    Member since:
    Aug 2013

    Posted 17 Jan 2014 Link to this post

    Hello,

    I'm having a very hard time importing an existing android certificate into icenium.

    All I have a is a keystore file from Eclipse which was generated when the app was first published. Now we've migrated over to Icenium and need to import the existing certificates.

    I've used the following command to convert the keystore to a p12:

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

    However, when I import it into Mist, it shows null expiration date. I have JDK1.7.0_25 installed. Any help is much appreciated!
  2. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 22 Jan 2014 Link to this post

    Hello Andrew,

    We have not been able to observe such abnormal behavior in our local tests and other users have reported successful convertion and usage inside Mist IDE. There was a similar bug to what you describe (that is already fixed) and it occurred whenever you try to import expired certificate - can you check whether this is not the case?

    Regards,
    Steve
    Telerik
    You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
    Looking for tips & tricks directly from the Icenium team? Check out our blog!
    Share feedback and vote for features on our Feedback Portal.
  3. Andrew
    Andrew avatar
    2 posts
    Member since:
    Aug 2013

    Posted 22 Jan 2014 Link to this post

    Hey Steve, 

    Thanks for your response.

    It appears this only happens in Mist. Here's an update: I had made sure that the converted certificate had a proper expiration date and everything, so I tried importing it through Graphite... it went through and I was finally able to build the apk with the correct certificate! However, this imported certificate still shows a null expiration date under Mist, so I'd assume it's a Mist-related issue of some sort.

    Thanks,
  4. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 23 Jan 2014 Link to this post

    Hi Andrew,

    Appreciate the clarification. We were able to reproduce the problem in our local tests and logged this in our bug tracker.

    Please excuse us for the inconvenience. Your Telerik points have been updated as token of gratitude for bringing this to our attention.

    Regards,
    Steve
    Telerik
    You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
    Looking for tips & tricks directly from the Icenium team? Check out our blog!
    Share feedback and vote for features on our Feedback Portal.
Back to Top