Software Archive
Read-only legacy content
17061 Discussions

Android signing certificate

Nir_B_
Beginner
2,204 Views

I am trying to update my Play Store apk, and I'm getting this:

Upload failed

You uploaded an APK that is signed with a different certificate to your previous APKs.

The APK I'm sending is written in Native, and signed by me. Apparently I need to sign this using the previous signing certificate signed by XDK building system.

Please! this is really urgent for me! I have a conference this week where it must be online.

Can someone please tell me where can I download the certificate? Or can someone please send me my the certificate?

Thank you,

Nir

 

0 Kudos
12 Replies
Amrita_C_Intel
Employee
2,204 Views

Previously you needed to email us, but now you can download your Android (and Crosswalk) keystore file directly. Goto this page https://appcenter.html5tools-software.intel.com/certificate/export.aspx and login (if asked) using your Intel XDK account credentials. You may have to go back to that location a second time after logging in (do this within the same browser tab that you just logged in with to preserve your login credentials).

If successful, there is a link that, when clicked, will generate a request for an "identification code" for retrieving your keystore. Pushing this link will cause an email to be sent to the email address registered to your account. This email will contain your "identification code" but will call it an "authentication code," different term but same thing. Use this "authentication code" that you received by email to fill in the second form on the web page, above. Filing in that form with the code you received will take you to a new page where you will see:

  • a "Download keystore" link
  • your "key alias"
  • your "keystore password"
  • your "key password"

Make sure you copy down ALL the information provided! You will need all of that information in order to make use of the keystore. If you lose the password and alias information it will render the key useless!

If the above fails, please send an email to html5tools@intel.com requesting help. It is important that you send that email from the email address associated with your Intel XDK account.

0 Kudos
Monish_O_
Beginner
2,204 Views

I followed the above, but got the following error:

jarsigner error: java.security.SignatureException: private key algorithm is not compatible with signature algorithm

0 Kudos
PaulF_IntelCorp
Employee
2,204 Views

Monish, do you mean that you used the keystore that you downloaded when you built your app and you are getting this "not compatible" message? Please clarify.
 

0 Kudos
Nick_d_
Beginner
2,204 Views

Hi Paul,

Is it possible that you can advise how I include the keystore into my app?

I have downloaded it from AppCentre and now need to include it. Really not sure how to do this.

Nick

0 Kudos
PaulF_IntelCorp
Employee
2,204 Views

Nick, if you are using the keystore that came from App Center and your existing account, just build with the XDK and that account. The signing certificate will be included automatically. Make sure the "Signed" box is checked in the Build Settings section of the Projects tab.

If you really need to sign it manually, there are lots of instructions in Stack Overflow and other forums. For example, http://stackoverflow.com/a/12567010

0 Kudos
Mrad_C_
Beginner
2,204 Views

Great, so this certificate is needed only when I update the app. The generated APK is signed against the retrieved one. Right?

0 Kudos
PaulF_IntelCorp
Employee
2,204 Views

Mrad -- once you publish an app all updates to that app must be signed with the same signing certificate. Currently, that signing certificate is automatically created for you when you create an account with the XDK. In the upcoming release that signing certificate will be made more accessible so you can download it and keep it someplace safe (which you should do). It also will allow for easier management of your certs. You can look at the EA release to see this in action, or wait a bit and you'll see it all in the next release of the XDK.

0 Kudos
siddharth_p_
Beginner
2,204 Views

ERROR ON UPDATE APP :signed with different certificate to your previous

0 Kudos
PaulF_IntelCorp
Employee
2,204 Views

You need to use your "converted legacy" certificate. When you logged into your account with 3088 or later, you are given the option to convert the Android certificate that was automatically created for your Android builds with an older version of the XDK into a certificate for use with the new version of the XDK. Please see the links above for more details.

0 Kudos
Renato_B_
Beginner
2,204 Views

I need to know how to recover the certificate password. i need to send an update and I cannot do it without the password and the problem is that I don't remember it. Please, some help.

0 Kudos
Renato_B_
Beginner
2,204 Views

Please, I really need some help here. I don't remember my certificate password and I need to update my app. I need to recover it or if it is not possible, I need another solution to upload the new version. 

0 Kudos
PaulF_IntelCorp
Employee
2,204 Views

Renato -- we do not store the passwords associated with your certificates, so we cannot recover your password. If you used a converted "legacy" Android certificate it may be possible to perform a second conversion so you can assign the password again. However, if you are talking about a new Android certificate that you created there is nothing we can do to help, because we do not store any password information and the password on a new Android certificate cannot be changed without knowing the old password.

If the certificate you are using is an iOS certificate you can simply generate a new one and upload that to the build system.

If the certificate you need access to is an Android certificate that was converted from a legacy Android certificate, send an email to html5tools@intel.com from the email address that is associated with your Intel XDK account and we may be able to help you there. What you need to request is that your account be configured to "reconvert your legacy certificate to a new certificate."

0 Kudos
Reply