Skip to main content
Pouradam
Inspiring
February 27, 2014
Answered

Make V2.0 of an Android App while V1.0 was made by JAVA!

  • February 27, 2014
  • 1 reply
  • 1104 views

Hi there!

it might be a simple question but I just don't have any experience in this case.

There is an App in Google play created one year back (by another designer) using JAVA (I suppose!)

Now I have re-designed that APP (from scrach as Version 2.0) using Flash CS6.

They want it to be concidered as an Ungrade Version (from V1.0 to V2.0) to let users receive an upgrade notification on their devices.

They have provided me the last version KeyStore file (and it's password)

The problem is, that file has no extention  (i.e it is not .p12 as needed by flash). So how should I use that KeyStore file to build my APK in Flash cs6 so that Google Play accept it as an Upgrde to the previous version??

By the way I just tried to add .p12 extention to that KeyStore file, but it was not acceptable by flash.

Should I convert this to .p12? if yes how?? or should I merge a code in the XML file? if yes what??

Thanks a lot for any comments and best of all.

Ali

This topic has been closed for replies.
Correct answer Colin Holgate

Well.... I am also on the same page with you Colin till now

I could successfully convert the old keystore to new .p12 using this code:

C:\Users\Ali>keytool -importkeystore -srckeystore MyOldKey -deststoretype PKC

S12 -destkeystore MyNewKey.p12

 

Enter destination keystore password:

Re-enter new password:

Enter source keystore password:

Entry successfully imported.

Import command completed:  1 entries successfully imported, 0 entries failed or

cancelled

And then I generated the APK with Flash cs6, WOW  

But...

uploading to the google play failed with these errors:

You uploaded an APK signed with a certificate that expires too soon.  ...

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

Your APK needs to have the package name of ...


The original certificate would have been made with a 25 year lifespan, which suggests that the conversion didn’t fully work.

How sure are you that the keystore is the one that was used a year ago? Do you still have the Java version, that you could do a tiny update to in order to check that it’s the right keystone?

If the command line approach doesn’t solve things you may have to create a new app. If you can update the Java one you could put in a promotion for the new app.

1 reply

Colin Holgate
Inspiring
February 27, 2014

I once spent several hours trying to convert a client’s keystore file into a P12 I could use. Gave up in the end, and just made my own P12. That wouldn’t help for your case.

One thing that I learned, but don’t remember trying (at least I didn’t succeed) is that you can use the command line to do the build. If you do that you are able to specify what kind of certificate file it is, which means you can use the original keystore file.

Pouradam
PouradamAuthor
Inspiring
February 27, 2014

Thanks a lot colin!

Right now I have no idea what should I do to generate the APK using command line, but I will investigate and give it a try and inform you (and others) the results hopefully.

By the way, Do you think it is OK that the keystore has no extention at all!??

thanks again, Ali

Pouradam
PouradamAuthor
Inspiring
February 27, 2014

Well.... I am also on the same page with you Colin till now

I could successfully convert the old keystore to new .p12 using this code:

C:\Users\Ali>keytool -importkeystore -srckeystore MyOldKey -deststoretype PKC

S12 -destkeystore MyNewKey.p12

 

Enter destination keystore password:

Re-enter new password:

Enter source keystore password:

Entry successfully imported.

Import command completed:  1 entries successfully imported, 0 entries failed or

cancelled

And then I generated the APK with Flash cs6, WOW  

But...

uploading to the google play failed with these errors:

You uploaded an APK signed with a certificate that expires too soon.  ...

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

Your APK needs to have the package name of ...