Android Question Problem with building AAB

[Andie]

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 ...

 

[DonManfred]

I have B4A v13.0, jdk-19.0.2

Did you updated the SDK TOO? This is mandatory for B4A 13.

What Version did you used before?
When (at what date) was your signkey created?

Is the signkey successfully configured in B4A 13?

 

[Andie]

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"

 

[DonManfred]

Yes, the SDK was updated.

i´m not sure about.

key algorithm not compatible with signature algorithm
Looks like the problem was an outdated SDK on the ones who discovered the same error.

 

[Andie]

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.

 

[Andie]

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

 

[teddybear]

@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.

 

[Erel]

Have you tried to explicitly set the algorithm:

#SignKeyAlgorithm: -digestalg SHA1 -sigalg SHA384withRSA

 

[teddybear]

Have you tried to explicitly set the algorithm:

#SignKeyAlgorithm: -digestalg SHA1 -sigalg SHA384withRSA

It works

 

[Andie]

Yes!!! Thank you very much!