Android Question pepk.jar - ExportEncryptedPrivateKeyTool has been compiled by a more recent version..

[Arf]

Hi,
I'm trying to update an older app on the play store, seems I have to update the sign key.
When I try launch ppk.jar from command line (win10 64) I get:
"ExportEncryptedPrivateKeyTool has been compiled by a more recent version of the java runtime (class file version 55.0), this version only recognises class file versions up to 52.0"

If I run java config on my PC, it says I am up to date. Any pointers?
Thanks.

 

[DonManfred]

If I run java config on my PC, it says I am up to date. Any pointers?

You are using an lower java than the one used to compile ppk.jar

Use a higher java version than java 8.
probably java 19 as B4A 13 requires v19... as of the error you probably need to use java 11+

 

[DonManfred]

List of Java class file format major version numbers?

I saw this list of major version numbers for Java in another post: Java Major version 23 67 22 66 21 65 20 64 19 63 18 62 17 61 16 60 15 59 14 58 13 57 12 56 11 55 10 54 9 53 8 52...

stackoverflow.com

 

[Arf]

Thanks, I have copied jdk-22 into my java directory and updated the path in B4A to point there, but how do I update my Windows Java version?
If I run java -version from command line it says 1.8.0_421-b09.

 

[DonManfred]

If I run java -version from command line it says 1.8.0_421-b09.

run java from the path the new java is installed

 

[Arf]

"run java from the path the new java is installed"

This enabled the tool to run. The other thing that required some figgerin' out was that you first get asked for a password for your keystore - enter it, characters you type are echoed as you type them. Then it asks for a password for b4a. I didn't know this, so tried pasting in the code google gave and all sorts of things, but eventually figured out you type in the same password as for your keystore, but when you do the second password, the characters are not echoed. Just type it in and press enter.

After all of this I updated another app, and did more reading first and found out that if you do wot the mighty Erel says HERE, then comile your app normally (not to aab), and upload the APK, then the key gets accepted and you don't need to mess about with the PEPK thing. Hope it stays that way.

 

[Erel]

If you have an app that was uploaded as APK and signed with an old key then you can continue to upload it as APK.