Build fail without error code

Solar2D Android
#21

Oh. OK. I found the error in build log on my mac, new keystore doesn’t work either…

                      [antcall] Exiting /Applications/Corona/Corona Simulator.app/Contents/Resources/build.xml.

                         [exec] Current OS is Mac OS X

                         [exec] Executing ‘jarsigner’ with arguments:

                         [exec] ‘-signedjar’

                         [exec] ‘MyCoronaActivity-signed.apk’

                         [exec] ‘-keystore’

                         [exec] ‘/Users/vlad/new.apptoonz.keystore’

                         [exec] ‘-storepass’

                         [exec] ‘mbwali’

                         [exec] ‘-sigalg’

                         [exec] ‘MD5withRSA’

                         [exec] ‘-digestalg’

                         [exec] ‘SHA1’

                         [exec] ‘MyCoronaActivity-unsigned.apk’

                         [exec] ‘apptoonz’

                         [exec] 

                         [exec] The ’ characters around the executable and arguments are

                         [exec] not part of the command.

Dec 18 08:01:27.612      [exec] jarsigner error: java.security.SignatureException: private key algorithm is not compatible with signature algorithm

Dec 18 08:01:27.976 Override ignored for property “sign.apk.via.command.line.result”

Dec 18 08:01:27.977      [exec] Result: 1

#22

This what I get on submission to play store

You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):[SHA1: 64:F6:F6:90:DE:14:9C:2F:E4:BA:88:D4:A1:99:24:CD:35:02:8F:96]and the certificate(s) used to sign the APK you uploaded have fingerprint(s):[SHA1: C2:73:78:81:75:2E:69:9E:B6:4B:9F:BC:38:0C:A8:B7:8D:E9:62:F9]

#23

Hey!

So, I was looking into what is going on, your key has “signature algorithm name: SHA1withDSA”, while all keys I have are “SHA256withDSA”. It seems that Java stopped supporting first one some time ago. I would suggest installing some old Java and JDK (6 or 7), make sure to uninstall current.

#24

No good. Downgraded to jdk-6u45 and still same result

#25

Are you sure all other versions of Java were removed?

Rob

#26

Please, make sure you have only java 6 installed. If that doesn’t work, may I ask you to try following:

replace c:\Program Files (x86)\Corona Labs\Corona\Resources\build.xml with this build.xml file. I was able to build with your original key using it.

#27

Well, success. I had made sure that only Java 6 was installed.

The new build.xml did the trick.

Thanks to Rob and Vlad for their patience on this.

#28

Was you able to submit without problems?

#29

Yes, worked as expected. Some issue about the age of my keystore I guess. Will have to have a new one for any new projects.

#30

With this build.xml you can encounter issues with newer Javas

#31

Hello! I’m sorry to bug you again, but it seems we don’t have any apps submitted with keys a you have. Would it be possible to try out this build.xml, which should work with all versions of Java and do the job of signing your app correctly (and failing if it didn’t).

If you can give it a quick try, I will be very glad, and if it works, we’ll ship it in next build.

#32

That build.xml file worked and was accepted by Google Play. I was using Java 6.

However I’m not publishing for a few days as I need to make more changes.

#33

Ok Rob and Vlad, I am having very similar issues. My original post is linked below if interested. Out of the blue, Saturday I started having issues on build 2017.3174 with small APK. As it stands now, I am still getting build error #1 on windows and small APK on MAC. So and alll, I’ve tried both build.xml files posted (plus original ones with install) in 3 different configurations as listed (see below).

Anything thoughts? Notes for on 2018.3193 say “Android: changing APK to support both modern and legacy keystores” which makes me thing something may have changed…  I’ll be glad to share my key and password if that helps.

Config #1 (Java 1.6.0_35  / Corona 2017.3184 )
 

[sharedmedia=core:attachments:7061]

As I try to compile for Android I get this error when my keystone password is requested (this is new behavior / same thing happened on debug key which is very odd ):

[sharedmedia=core:attachments:7062]

To make sure I am sane, I checked my password on the same file:

[sharedmedia=core:attachments:7063]

Config #2 (Java 1.8.0_151  / Corona 2017.3184  / Windows)

(Same build error as orignal post)

Sanity check the password and versions:

[sharedmedia=core:attachments:7064]

Config #3 (Java 1.8.0_151  / Corona 2017.3184  / MAC)

No errors be a small APK 50KB in size.

Original inquiry:
https://forums.coronalabs.com/topic/71428-build-error-1-with-only-one-of-our-signing-keys-after-updating-to-latest-public-release/

#34

Thanks, Conor. That worked!!! Not sure where your comment went but you provided the solution. For anyone else out there.

 

Corona 2017.3189 - Nothing newew, doesn’t work

jdk1.6.0_45 

 

That’s it!

 

Missing conor message:

In case this helps. My problem ended up being using an old keystore (2012) and a new Java installation. Vlad provided a temporary fix, but now the fix is in latest (3189) daily build. All works fine for me now.
#35

Are you saying that 3193 and later do not work?

Rob

#36

Hey guys. I believe, at this point Java 1.8+ and 3194+ should work for any keystore. Can someone verify this?

#37

Sorry for my poor English skill. This morning, all was well when using this combination of Java and Corona:

 

Corona 2017.3189 

jdk1.6.0_45 

 

Suddenly at GMT ( UTC ): 9:30 AM (9:30) without I was no longer able to compile (getting build error #1). I honestly did not change thing on my computer. Can you confirm if or not the build servers got update at that time by any chance?

 

So now, I’ll Java 1.8+ and 3194+. and I’ll let you know shortly.

#38

I am able to compile but my app gets rejected every time… here’s everything I did tonight:

====

==== Part 1 (Upload error)

====

So, I installed the following:

Corona 2017.3195 jdk-8u151-windows-i586.exe (java version "1.8.0\_151")

And although it compiles when I upload the apk to Google, here’s what I get:

[sharedmedia=core:attachments:7067]

====

==== Part 2 (same error on upload)

====

So… then i try this

cd C:\Program Files (x86)\Java\jdk1.8.0\_151\bin keytool -importkeystore -srckeystore D:\Rabbit\Documents\Keystore\AlexFireRabbit.store -destkeystore D:\Rabbit\Documents\Keystore\AlexFireRabbitUPGRADED.keystore

Then compile with the new key “UPGRADED”, I get the same when i upload: 

[sharedmedia=core:attachments:7067]

====

==== Part 3 (same error on upload)

====

At this point, I make sure I did things correctly on the new key (which is good but shows a warning):

keytool -v -list -keystore D:\Rabbit\Documents\Keystore\AlexFireRabbitUPGRADED.keystore 

This works but I see a warning:

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 D:\Rabbit\Documents\Keystore\AlexFireRabbitUPGRADED.keystore -destkeystore D:\Rabbit\Documents\Keystore\AlexFireRabbitUPGRADED.keystore -deststoretype pkcs12"."

So… the next command I try of course:

keytool -importkeystore -srckeystore D:\Rabbit\Documents\Keystore\AlexFireRabbitUPGRADED.keystore -destkeystore D:\Rabbit\Documents\Keystore\AlexFireRabbitUPGRADEDevenmore.keystore -deststoretype pkcs12

And make sure the warning is gone using this command (which it):

keytool -v -list -keystore D:\Rabbit\Documents\Keystore\AlexFireRabbitUPGRADEDevenmore.keystore 

The result is same on upload.

Any ideas?

#39

May I ask to try old keystore, not upgraded?

#40

I have. That is part #1. Using my original keystore from 2012.