Dec 27, 2017 Replies: 2 Private sign keys created with B4A v7.80 or less together with Java 8u151+ will fail with the above error message. Note that it does not affect existing keys. It is related to a change in the default key size. It is fixed for the next update of B4A. As a workaround you can switch to Java 8u144: http://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html Or create the key from the command line: Code: keytool -genkey -dname "CN=Unknown,O=Unknown,C=Unknown" -keystore mykeystore.keystore -keysize 1024 -alias b4a -validity 14000 -keypass 123456 -storepass 123456 123456 that appears twice should be replaced with the password. Click to expand...
Private sign keys created with B4A v7.80 or less together with Java 8u151+ will fail with the above error message. Note that it does not affect existing keys. It is related to a change in the default key size. It is fixed for the next update of B4A. As a workaround you can switch to Java 8u144: http://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html Or create the key from the command line: Code: keytool -genkey -dname "CN=Unknown,O=Unknown,C=Unknown" -keystore mykeystore.keystore -keysize 1024 -alias b4a -validity 14000 -keypass 123456 -storepass 123456 123456 that appears twice should be replaced with the password.
konradwalsh Active Member Licensed User Longtime User Mar 12, 2018 #2 Since I am on v7.80 and v8.00 has been released but I didnt receive an email, I assume there wont be an in between update to fix this issue? I guess I am not eligible for v8.00
Since I am on v7.80 and v8.00 has been released but I didnt receive an email, I assume there wont be an in between update to fix this issue? I guess I am not eligible for v8.00
Erel B4X founder Staff member Licensed User Longtime User Mar 12, 2018 #3 konradwalsh said: I assume there wont be an in between update to fix this issue? Click to expand... Sorry but no. However the workaround explained in the first post is quite simple.
konradwalsh said: I assume there wont be an in between update to fix this issue? Click to expand... Sorry but no. However the workaround explained in the first post is quite simple.
