Can't update my app anymore

[waltsir]

I always imported .aab file to update my apps but now I get this message “To import bundle you need to subscribe to Application Signature Play service”

So, I go to “manage et protect you Application Signature Key”,

• I download the public key “encryption_public_key.pem” and the “pepk.jar” tool because to create a private key I have to do:

$ java -jar pepk.jar --keystore=foo.keystore --alias=foo --output=encrypted_private_key_path --rsa-aes-encryption --encryption-key-path=/path/to/encryption_public_key.pem

Not sure to know where I copy this text, I begin to start “pepk.jar” from Windows but get this message “a Java exception has occured”

OMG, it becomes so complicate now to do just an update ;(( What’s wrong!?

v.2025.3721

[chodongwon82]

I feel you — I think I ran into a very similar issue some time ago, but it’s been a while so I can’t recall the exact steps. I remember I eventually managed to solve it through a bit of Googling and luck. These days, I’d probably turn to ChatGPT for help — it might be able to guide you more clearly through the process. Hope it gets sorted out soon!

[waltsir]

You mean the “Application Signature Key” with private key is obligatory now to update apps on Google Console? Because I never did previously or it’s a problem with apk/aab generated by Corona?

[waltsir]

I put both files pepk.jar and encryption_public_key.pem simply to c:\ then I started from console but I get this error:

I don’t understand what’s the problem , I have the lastest Java version (8- 461)

EDIT: same error if I just write C:> java -jar c:\pepk.jar

[chodongwon82]

It’s been a long time, so my memory is a bit fuzzy, but in my case, the “pepk.jar” file provided by Google didn’t work properly. I think I ended up downloading another version of “pepk.jar” I found through Googling. After replacing the file, the command seemed to work. Sorry I can’t remember the details more clearly!

[waltsir]

ok, but I downloaded others , same problem. I read that I maybe need not java 8, but 9 or more to make compatible with this jar

[chodongwon82]

pepk.jar (8.7 MB)
Would you like to try using this file? Best of luck!
I used this file along with the command below.
java -jar pepk.jar --keystore=“C:\aaa.keystore” --alias=aaa --output=“C:\abc.pem” --rsa-aes-encryption --encryption-key-path=“C:\encryption_public_key.pem”

[waltsir]

Thanks but same problem, even if I just write java -jar pepk.jar with your file.

What version of Java do you have ?

[chodongwon82]

Ah, sorry to hear that it didn’t work.

C:\>java -version
openjdk version "11.0.20" 2023-07-18
OpenJDK Runtime Environment OpenLogic-OpenJDK (build 11.0.20+8-adhoc..jdk11u)
OpenJDK 64-Bit Server VM OpenLogic-OpenJDK (build 11.0.20+8-adhoc..jdk11u, mixed mode)

[waltsir]

Not the same specs than you and I have the lastest version of Java 8…

PS C:> java -version
java version “1.8.0_461”
Java™ SE Runtime Environment (build 1.8.0_461-b11)
Java HotSpot™ Client VM (build 25.461-b11, mixed mode, sharing)

I see that Java 8 can be updated to Java JDK24, that’s maybe the workaround…

I just installed it and went further , it asked my password for the key.store then for the key but again an error:

The problem is that I only have one password, which I use for .keystore but it asks a password for alias too.

[kakula]

This Might help:

just go to your windows user folder if you are using windows

delete android and gradle folders

try to build (this time it will take much longer to download those folders)

This might solve your problem

[waltsir]

Thanks but it changes nothing
By the way, I don’t know what input when asking “alias” password. I just have one for the .keystore, which I use for building with Solar2D.

Well, I think I have to try on another computer if the problem comes from my Windows.

[colinmorgan]

I think you need to use JRE 6.

Java Archive Downloads - Java SE 6

[kakula]

did you download JDK 16? did you export keystore file and assign password?

just go to this folder:

C:\Program Files\Java\jdk-16.0.2\bin

and create a batch file there and edit its content to:

keytool -genkey -v -keystore com.yourappname.something.something.keystore -alias aliasname -keyalg RSA -validity 999999

and this (com.yourappname.something.something) must match Package name in solar2d when you build the app

then run your batch file … it will prompt you for a few info including the password (twice)

take the created file in this same folder place it somewhere and keep it

then when building from solar2d browse to the file and give same package name, it will ask you for the password … then your problem should be solved

[waltsir]

Hello, I think I need to create another keystore with the same working JDK I downloaded yesterday v.24 (or v.16, why not). Maybe there’s a conflict between the version with the JDK I used to create my keystore (JDK 8) and the JDK version I downloaded to make work pepk.

I’ll try that and let you know. Thanks

[kakula]

i used JDK 16 to create keystores days ago for a couple of apps and published them successfully to google … so hopefully it will work

[waltsir]

ok, I’m going to recreate another keystore with JDK16.
By the way, then you didn’t have problem to create the private key asked by Google with that keystore?

Where do I find the 2nd password ???
Enter password for store ‘foo.keystore’: — this ok I know it, it’s which I used when I created the keystore with keytool
Enter password for key ‘fookey’: —> but this one ??

[waltsir]

Here’s video that shows more than all my explanations

[kakula]

is this an old app? because i faced this today, and i eventually used the original keystore for it

[waltsir]

Yes, this is an old app (January 19, 2025).

For the new apps, I don’t need to do all that (don’t need to use pepk to create a private signature), all is done automatically directly on Google Publish.

I tried with the original keystore but same problem.
Well, I give up, and publish this old app as a new app instead of trying to do an update.
Thanks for all