gradle build error with 1024bit key about adobe-runtime-support HOT 5 OPEN

Hi, You'll likely want to update to a 2048bit cert as Java doesn't support these older ones anymore. If you are worried about a cert change on the Play Store, you can use the technique I've outlined here: https://airsdk.dev/docs/tutorials/platform/android/handling-1024bit-certificates

from adobe-runtime-support.

Unfortunately I need to support other markets with .apk format. In Google Play I done it few years ago and it is ok now.

Why does it work with AIR33.1.1.935 with same adt.cfg?

from adobe-runtime-support.

What other markets are you supporting? Most of them have something similar or allow you to change the certificate.

Unsure why it works with the older SDK, could be using a different version of Java (v1.8 should still work with these older certificates)

from adobe-runtime-support.

I would be interested in the ADT log output from building with the older AIR SDK. The likely reason here though is that you're building using Gradle, and the recent versions of this need JDK 11 so we are specifically looking for that within ADT now. The error you're seeing with the signing is a Gradle error...

Although having said that: we did change how the signing is done, to switch over to using Gradle (because of all the issues we were having with Oracle removing support for the sun security packages). So this is likely to be why it's Gradle that's showing the error, and an earlier release was working.

Which may mean that we can change this back (we've changed some things over to use BouncyCastle libraries for signing, although I guess we should check first whether they support 1024-bit keys!) .. we can try checking this.

In the meantime -> if you create an AAB file instead of an APK, it should work, and then you would be able to split the AAB into APKs and re-sign manually via Java 8?

thanks

from adobe-runtime-support.