Error Code 256 - MyCoronaActivity-signed-aligned.apk

Solar2D Android
#21

Ok, i did test it (using keystore-explorer, very nice tool). There is an expiry date, but it is currently set in year 4173, so we should be fine for now on that side.
I had another copy of the keystore, i tried it as well and same problem occurred (i was thinking maybe the keystore i was using was somewhat corrupted, but that is not the case, as this other version produces exactly the same results).

When i load the keystore, i get this in the console : 

Testing credentials for '/Users/dim/gDrive/Vooter\_Founders/Android Keystore/vooter.keystore': Picked up JAVA\_TOOL\_OPTIONS: -Duser.language=en jar signed.

Is this normal ?

Thanks for the help,

Dim

#22

How old is the keystore?

What version of Java JDK do you have installed?

Rob

#23

I am not sure about the creation date, but the last time it was modified was the 08/20/2015.

Here is the copy of terminal regarding the Java JDK: 

dim:~ dd$ java -version java version "1.8.0\_101" Java(TM) SE Runtime Environment (build 1.8.0\_101-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)

Thanks Rob,

Dim

#24

If you’re using 3184, try installing the latest Java and see if that helps.

Rob

#25

Hello Rob,

Installing the latest Java did not fix it. However, a new information popup in the console log, at the start, about the keystore : 

Warning: The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /Users/dim/Desktop/vooter.keystore -destkeystore /Users/dim/Desktop/vooter.keystore -deststoretype pkcs12". Picked up JAVA\_TOOL\_OPTIONS: -Duser.language=en jar signed. Warning: The signer's certificate is self-signed. Using java version "9.0.1" Java(TM) SE Runtime Environment (build 9.0.1+11) Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode) Building Android app for dimd@hotmail.com with 2017.3184 Using custom build id from app bundle: 00000 (AppSettings.lua) BUILD SUCCESSFUL Total time: 0 seconds BuildID: 5a3509fd814bd [echo] "creating unsigned.apk" [exec] Result: 1 [exec] Result: 1 BUILD FAILED /Applications/CoronaSDK/Corona Simulator.app/Contents/Resources/build.xml:514: Warning: Could not find file /var/folders/3h/w0qklgtj77j839lf978c3jh80000gn/T/CLtmpN6V8WM/MyCoronaActivity-signed-aligned.apk to copy. Total time: 7 seconds Android build failed (256) after 77 seconds ERROR: Build Failed: Error code: 256

So i tried to update the keystore using the command proposed, but i received this error : 

keytool error: java.lang.Exception: The destination pkcs12 keystore has different storepass and keypass. Please retry with -destkeypass specified.

And finally, using the -destkeypass, for some reason it only worked when i picked the same password as for the keystore, not sure why.
 

I finally could build, but i still have this info in the console, about the unsigned .apk : 
 

BUILD SUCCESSFUL Total time: 0 seconds BuildID: 5a350f68f0e18 [echo] "creating unsigned.apk" BUILD SUCCESSFUL Total time: 9 seconds Android build succeeded in 71 seconds

Does that seem normal ?

Sorry if the questions or comments don’t make much sense, i am not yet fully grasping the whole concept of keystores.

Dim

#26

I believe that’s just an intermediary message. We create an apk file then sign it, so it’s probably not an error,

Rob

#27

Ok great then. I’ll keep an eye on the message for the next daily builds.

Thanks a lot for the help Rob,

Dim

#28

I also get the “creating unsigned.apk” with a successful android build using corona build 3301.

So to confirm, we can just disregard the message?

I am using java version “1.8.0_121”

#29

Yes, you can ignore that message. It doesn’t way “Error” or “Warning”, so it’s just informational where we are logging the steps to build an app and one of those is creating an unsigned APK.

Rob