Android Question Problem with building AAB

A

Andie

Member
Licensed User
Longtime User
I have B4A v13.0, jdk-19.0.2, android-34-SDK, targetSdkversion = 34.
At the end of the AAB building process this message is displayed:

Building app bundle (1.15s)
Signieren der AAB-Datei Error

jarsigner-Fehler: java.lang.IllegalArgumentException: key algorithm not compatible with signature algorithm


The code was not changed. Maybe, I'm not the only one with this problem ...
 
Sort by date Sort by votes
A

Andie

Member
Licensed User
Longtime User
Yes, the SDK was updated.
The version before was 12.80.
The sign-key was created in February, 2022
What do you mean by "successfully configured in B4A 13", DonManfred? I have to use this key, which was built 2 years ago, otherwise Google Play will say: "wrong sign-key"
 
Upvote 0
A

Andie

Member
Licensed User
Longtime User
Well, I have an android-34 folder and I set the path to its android.jar file. I also have the newest command-line-tools. No idea, what might be wrong.
 
Upvote 0
A

Andie

Member
Licensed User
Longtime User
UPDATE:
I switched back to jdk-14.0.
And now the signing of the AAB works!!!
CONCLUSION (maybe I'm wrong):
Something strange happens within jdk-19.0.2
 
Upvote 0

teddybear

Well-Known Member
Licensed User
@Erel, Perhaps this is a bug. we created the private sign key using algorithm SHA384withRSA(V13.0) or SHA256withRSA(V12.8- ), but building AAB jarsigner -sigalg using algorithm is SHA1withDSA in V13.0.
 
Last edited:
Upvote 0
You must log in or register to reply here.
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…