APK update version, build in another software

Solar2D Android
#1

Hello.

Last night i tried for the first time, upload a apk to google store, an apk build in Corona. I´m already a user of google play. I was trying to update a “old” simple program that i have in google play. I put the package name… version… 

I read something about signing the apk, it´s is needed to go to the java folder and sign the apk…

But when i upload the apk google send a message that the old apk as a diferent key (i think was that words) from the one i was trying to upload. And google show me a line of char (i think in hexadecimal).

Is possible to put that information in corona, for that google recognize the new apk as a update?

Or… is possible to update a apk generated in other software, at generic way?

Thanks.

#2

Once you publish an app on Google Play, you have to use the same “keystore”. If you have your original version, you should be able to point Corona to that keystore and have it use it. If you don’t have access to the original keystore, then you will likely have to create a new app in Google Play with the new keystore. I don’t know why Google has this requirement because it’s too easy to loose your keystore file.

Rob

#3

Hello.

I´ve found in the other program that i used to produce the old apks, a file, is “Key.pk8” is incrypted.

Corona does not associate automatically to this extension is own “keystore” on the build menu.

Is possible be the same thing, but with different extensions for the file??? Is a small file, with 1.18kb.

#4

This might help.

http://stackoverflow.com/questions/39657812/how-to-import-x509-pem-pk8-file-into-jkskeystore

Rob

#5

Hello, not still tryed, the item befor, the generation on other software…

I´m trying to sign other, new in Corona Labs.

Already put the apk in the java folder ( and the apk in the default folder generated by Corona), and nothing, gives me this error…

How is so difficult to sign a apk?

Generating 2.048 bit RSA key pair and self-signed certificate (SHA256withRSA) with a validity of 999.999 days

        for: CN=Jose Coimbras, OU=Unknown, O=Unknown, L=Lisboa, ST=Unknown, C=Unknown

Enter key password for <AppDiscurso>

        (RETURN if same as keystore password):

[Storing Discursoempresas.keystore]

keytool error: java.io.FileNotFoundException: Discursoempresas.keystore (Acesso negado)

java.io.FileNotFoundException: Discursoempresas.keystore (Acesso negado)

        at java.io.FileOutputStream.open0(Native Method)

        at java.io.FileOutputStream.open(FileOutputStream.java:270)

        at java.io.FileOutputStream.<init>(FileOutputStream.java:213)

        at java.io.FileOutputStream.<init>(FileOutputStream.java:101)

        at sun.security.tools.keytool.Main.doCommands(Main.java:1144)

        at sun.security.tools.keytool.Main.run(Main.java:343)

        at sun.security.tools.keytool.Main.main(Main.java:336)

#6

You don’t manually sign our apps. We sign them for you. In the build dialog, there is a field for “Keystore” and “Key Alias”. Once you have your keystore created (which does require you to access the system command line and on Windows, it’s a pretty tough command to type in), you just make sure those two fields are filled in and you have a valid folder (that’s not your project folder) to build to (Save to Folder) and you should have a properly signed APK that you can upload to Google Play.

Are you on Windows or a Mac?

Rob

#7

Hello.

I´m in Windows.

I can´t have sucess in signing the app with the build from Corona. I just can do it with an external utility (i can´t give you the name, is in my home computer). I build the apk, and then sign it… 

Sorry, i must been doing something wrong. I´m only a curious part/time programmer. By these days i just had the need to ensure that i can make a corona app and sign it. I achieve it, maybe not be the best way… With some time i need to try again sign it with corona…

Thanks for the time you spend with me.

#8

Well, i´ve made a lot of tries, onlinde decoders etc… no way to put it solved. Is possible to anyway by the rsa that is in the google play, include someway in code, to “aproved” signed? I cant see the light.

As i´ve wrote before, i have a apk that was “auto signed” by the program that generates the apk, now with corona intents to update it, bu google says its not the same…

Thanks.

#9

Although we encourage you to develop and publish a single APK that supports as many device configurations as possible, doing so is sometimes not possible. To help you publish your application for as many devices as possible, Google Play allows you to publish multiple APKs under the same application listing. Google Play then supplies each APK to the appropriate devices based on configuration support you’ve declared in the manifest file of each APK.

By publishing your application with multiple APKs, you can:

  • Support different OpenGL texture compression formats with each APK.
  • Support different screen sizes and densities with each APK.
  • Support different device feature sets with each APK.
  • Support different platform versions with each APK.
    How Multiple APKs Work

The concept for using multiple APKs on Google Play is that you have just one entry in Google Play for your application, but different devices might download a different APK. This means that:

  • You maintain only one set of product details (app description, icons, screenshots, etc.). This also means you cannot charge a different price for different APKs.
  • All users see only one version of your application on Google Play, so they are not confused by different versions you may have published that are “for tablets” or “for phones.”
  • All user reviews are applied to the same application listing, even though users on different devices may have different APKs.
#10

Once you publish an app on Google Play, you have to use the same “keystore”. If you have your original version, you should be able to point Corona to that keystore and have it use it. If you don’t have access to the original keystore, then you will likely have to create a new app in Google Play with the new keystore. I don’t know why Google has this requirement because it’s too easy to loose your keystore file.

Rob

#11

Hello.

I´ve found in the other program that i used to produce the old apks, a file, is “Key.pk8” is incrypted.

Corona does not associate automatically to this extension is own “keystore” on the build menu.

Is possible be the same thing, but with different extensions for the file??? Is a small file, with 1.18kb.

#12

This might help.

http://stackoverflow.com/questions/39657812/how-to-import-x509-pem-pk8-file-into-jkskeystore

Rob

#13

Hello, not still tryed, the item befor, the generation on other software…

I´m trying to sign other, new in Corona Labs.

Already put the apk in the java folder ( and the apk in the default folder generated by Corona), and nothing, gives me this error…

How is so difficult to sign a apk?

Generating 2.048 bit RSA key pair and self-signed certificate (SHA256withRSA) with a validity of 999.999 days

        for: CN=Jose Coimbras, OU=Unknown, O=Unknown, L=Lisboa, ST=Unknown, C=Unknown

Enter key password for <AppDiscurso>

        (RETURN if same as keystore password):

[Storing Discursoempresas.keystore]

keytool error: java.io.FileNotFoundException: Discursoempresas.keystore (Acesso negado)

java.io.FileNotFoundException: Discursoempresas.keystore (Acesso negado)

        at java.io.FileOutputStream.open0(Native Method)

        at java.io.FileOutputStream.open(FileOutputStream.java:270)

        at java.io.FileOutputStream.<init>(FileOutputStream.java:213)

        at java.io.FileOutputStream.<init>(FileOutputStream.java:101)

        at sun.security.tools.keytool.Main.doCommands(Main.java:1144)

        at sun.security.tools.keytool.Main.run(Main.java:343)

        at sun.security.tools.keytool.Main.main(Main.java:336)

#14

You don’t manually sign our apps. We sign them for you. In the build dialog, there is a field for “Keystore” and “Key Alias”. Once you have your keystore created (which does require you to access the system command line and on Windows, it’s a pretty tough command to type in), you just make sure those two fields are filled in and you have a valid folder (that’s not your project folder) to build to (Save to Folder) and you should have a properly signed APK that you can upload to Google Play.

Are you on Windows or a Mac?

Rob

#15

Hello.

I´m in Windows.

I can´t have sucess in signing the app with the build from Corona. I just can do it with an external utility (i can´t give you the name, is in my home computer). I build the apk, and then sign it… 

Sorry, i must been doing something wrong. I´m only a curious part/time programmer. By these days i just had the need to ensure that i can make a corona app and sign it. I achieve it, maybe not be the best way… With some time i need to try again sign it with corona…

Thanks for the time you spend with me.

#16

Well, i´ve made a lot of tries, onlinde decoders etc… no way to put it solved. Is possible to anyway by the rsa that is in the google play, include someway in code, to “aproved” signed? I cant see the light.

As i´ve wrote before, i have a apk that was “auto signed” by the program that generates the apk, now with corona intents to update it, bu google says its not the same…

Thanks.

#17

Although we encourage you to develop and publish a single APK that supports as many device configurations as possible, doing so is sometimes not possible. To help you publish your application for as many devices as possible, Google Play allows you to publish multiple APKs under the same application listing. Google Play then supplies each APK to the appropriate devices based on configuration support you’ve declared in the manifest file of each APK.

By publishing your application with multiple APKs, you can:

  • Support different OpenGL texture compression formats with each APK.
  • Support different screen sizes and densities with each APK.
  • Support different device feature sets with each APK.
  • Support different platform versions with each APK.
    How Multiple APKs Work

The concept for using multiple APKs on Google Play is that you have just one entry in Google Play for your application, but different devices might download a different APK. This means that:

  • You maintain only one set of product details (app description, icons, screenshots, etc.). This also means you cannot charge a different price for different APKs.
  • All users see only one version of your application on Google Play, so they are not confused by different versions you may have published that are “for tablets” or “for phones.”
  • All user reviews are applied to the same application listing, even though users on different devices may have different APKs.