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