Was you able to submit without problems?
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.
With this build.xml you can encounter issues with newer Javas
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.
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.
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/
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.Are you saying that 3193 and later do not work?
Rob
Hey guys. I believe, at this point Java 1.8+ and 3194+ should work for any keystore. Can someone verify this?
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.
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?
May I ask to try old keystore, not upgraded?
I have. That is part #1. Using my original keystore from 2012.
Hi Vlads, This is a real problem for me as need to update my app before Jan 15. Anything you can do to help would be much appreciated. I also willing to share my keystore and psw (email me)… whatever helps!
Alex
Ah! Finally got somewhere. I need SHA1withDSA!
So, whatever version of Corona (from 3184+) I compile with the debug key and I get an APK that works. From this APK, I re-sign with my old/original keystore manually (with SHA1withDSA… the option I have for my old keystore). The resulting file I can uploaded and is accepted. Can you make it so corona does this works for me please?
Here’s how I have to do it now until Corona can help, if possible:
First remove debug signing from apk:
zip -d other2.apk 'META-INF/\*.SF' 'META-INF/\*.RSA'
Second, re-sign with correct signature algorithm and key:
jarsigner -verbose -sigalg SHA1withDSA -digestalg SHA1 -keystore D:\Rabbit\Documents\Keystore\AlexFireRabbit.store C:\temp\other2.apk keyforalexfirerabbit
And as always, zipalign for Google:
.\zipalign -v 4 other2.apk other4.apk Thanks, [member=‘firerabbit.info’]. This is very cool! Glad you could figure it out. I incorporated changes in this build.xml as a fallback. Could you give it a try?
You are the MAN!!! The build.xml provided didn’t work BUT I created a new one based on it. Obviously what I did is wrong where I changed all the build targets to suit me 
Search for “@Vlads” to find my changes.
Anyways. Thank you so, so much for the extra support and effort Vlads! We really appreciate this very much, you have no idea. I literally jumped out of my chair when I saw this work just now.
So happy! If you need me to test another build.xml, I am here for you!
Alex
Oh… It wrote SHA1with R SA instead of SHA1with D SA, silly typo. Could you please give it a try: build.xml?
Actually, you could change only 1, they’re fallbacks to each other.
Yes, that build.xml worked like a charm including uploading to Google. Thank you! 
Alex
PS: Corona 2018.3197 is working perfect for Android builds on MAC and WINDOWS.
100% satisfied over here. Thank you
Alex