topic I signed the updated with the in Software Archive

Keystore

Samuel_G_1 — Wed, 09 Sep 2015 17:16:24 GMT

I am building my app with a different toolkit.

I requested my keystore...and did get it downloaded with the passwords. However, when I build my app, and use Jarsigner to sign it, then try to upload it to GooglePlay, I get an error about the new and old certificates not matching.

Why?

--Sam

Hello,

Amrita_C_Intel — Wed, 09 Sep 2015 17:51:46 GMT

Hello,

This might help you.

http://stackoverflow.com/questions/4843212/the-apk-must-be-signed-with-the-same-certificates-as-the-previous-version

Or this one

Amrita_C_Intel — Wed, 09 Sep 2015 17:53:12 GMT

Or this one

https://www.scirra.com/tutorials/1353/how-to-export-and-build-your-games-with-intel-xdk-crosswalkphonegap

Attached is the output from

Samuel_G_1 — Thu, 10 Sep 2015 12:55:29 GMT

Attached is the output from Jarsigner on both APKs. I built the new one, and signed it with the keystore Intel sent me.... If you look, the CN is different and the dates are different...

So, what's the issue?

Did you sign the upgrade with

Pamela_H_Intel — Thu, 10 Sep 2015 21:20:46 GMT

Did you sign the upgrade with a different key than the key you used for the original version of your app?

I signed the updated with the

Samuel_G_2 — Fri, 11 Sep 2015 00:58:27 GMT

I signed the updated with the Key that INTEL sent me...the same key that was used by INTEL for the original version of my app.

Anyone at INTEL have any

Samuel_G_1 — Fri, 11 Sep 2015 17:59:23 GMT

Anyone at INTEL have any thoughts on this???

My thought is that you got

PaulF_IntelCorp — Fri, 11 Sep 2015 22:50:25 GMT

My thought is that you got sent the wrong cert. The first one looks like a cert that could have been generated by the XDK. Did you use an "organization name" of BTST with your old account? If so, that first one is from your old account. The second one has a weird CN name in it, there is a "N/A" which I interpret as "not available" followed by what appears to be either an "SCC" or "SGG" -- it's hard to see, the screen shot you posted is very lo-res.

Do you still have access to your XDK account? If so, when you build an app with that account, what does the CN name look like?

Paul, et al.

Samuel_G_1 — Mon, 14 Sep 2015 13:00:31 GMT

Paul, et al.

The APP ID for this application is : com.nascg.nascg.btstupload

The NASCG(s) are left over from when I originally registered waaaaaay back when this was an AppMobi project. Back then, for some reason the registration setup got things confused...and I never had any desire to change it...it works.

So, the second jarsigner output is the 'REAL' signature information (signed when building with the XDK). The first one is what I get when I sign the app with the signature info Intel provided to me.

If you think I somehow got the wrong certs, then please resend.

--Sam

Sam ~

John_H_Intel2 — Mon, 14 Sep 2015 14:46:02 GMT

Sam ~

I am sending you and email.

John,

Samuel_G_1 — Mon, 14 Sep 2015 14:47:10 GMT

John,

I just got finished trying a new keystore, which worked for uploading to GooglePlay.

Thanks,

Sam