jarsigner: Certificate chain not found for: mykey.
939 views
Skip to first unread message
Jerome Y
unread,
Jan 26, 2015, 2:57:27 PM1/26/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to appto...@googlegroups.com
Hi, I am on an epic journey to try to update an app created with the Classic AI about 3 years ago. I have revised the app in AP2, but cannot upload it because of repeated keystore errors. Originally all was packaged using Marketizer. I have retained the keystore from Marketizer as well as downloaded the keystore from AI Classic... somehow I should be able to add this to the apk from AI2.
I cannot upload either of these keystores directly to AI2 and have it produce and aka that is accepted by the Play Store... error is the keystore not being the same as the original.
On advice I am trying to do this in AppToMarket but getting the error:
26Jan2015_1146.32: SUCCESS: The new .apk was generated: C:\Users\Lab\Desktop\AppToMarket_v32\myApks\XXX_new.apk
26Jan2015_1146.37: BUTTON CLICKED: 4> Sign
26Jan2015_1146.37: Signing the application...
26Jan2015_1146.37: jarsigner: Certificate chain not found for: mykey. mykey must reference a valid KeyStore key entry containing a private key and corresponding public key certificate chain.
26Jan2015_1146.37: ERROR: There was error in signing your app
Originally the alias was myalias and that also did not work with same error. This is using the keystore downloaded from AI Classic....
ANY IDEAS???? I think I have all the parts need to make this work... hate to use a new App as I have a user base.