Yes that’s all that shows.
Normally I would have expected hundreds of lines. I checked my build and I only got one line too. I’ve shared it with the engineers.
Has anyone tried dropping back to 1093 or found an earlier version that works. Is everyone having problems on Windows or is it happening to Mac people too?
Dropped back to 1093 and it’s exactly the same:
[exec] Result: 1
[exec] Result: 1
and no apk file in directory
Dropped back to 1092 and it is finally working!
And there are no [exec] Result: 1 outputs in the console window
Builds 1093, 1094 and 1095 are still not returning the APK as of this morning
It’s now been two days that I and others are having this issue.
Is there any word yet on a fix? As I cannot build Android apps.
I’m stuck between a rock and a hard place as I need this fix from 1094:
Android: Fixed bug where store.target and
system.getInfo(“targetAppStore”) would always return “none” as of daily
build #1088, which also broke automatic download of expansion files.
And cannot roll back as I need:
Core: Add physics.reflectRay() to Lua.
A quick note to let you know that I generated APK file using Daily Build 1094 just now. I’m on Mac. I wonder if there are others with Windows who are able to (or unable to) build APK…
Naomi
Just tried again using a Mac.
Build 1089: apk generated no problem.
Build 1095: apk not generated. received [exec] Result: 1
Alex
Hi Alex, thanks for the update. Can you build the Hello World sample app and post your Mac’s log output, as it may have clues.
Hi Alex,
Can you provide a system profiler dump from your Mac?
http://guides.macrumors.com/System_Profiler#Exporting
Thanks,
Brent
Hello World also did not work. Got the same [exec] Result: 1 output.
What information from my system profiler do you need? A full export is 4.5mb of xml text.
Ok, this is very odd.
Just tried it on my Mac, and get the exact same error as on my PC and same as Poon.
Poon are you a beta tester like myself? Just curious as it only seems to be affecting only a few people.
Strange how it’s the same on both my PC and Mac.
Nope, I’m not a beta tester. I have Corona Pro.
I’ve tried two different Macs, both with the same result. Did not try Windows.
Hi Alex,
Can you compress the entire XML file and e-mail it to me? I know it’s a large file, but I’d like to see the entire contents. Email is brent (at) coronalabs (dot) com.
Thanks,
Brent
Hi Brent, it should be in your inbox.
Thanks Alex! I received it and forwarded it to the engineers investigating this issue.
Brent
Hi Brent.
I have made some progress in getting to the bottom of what’s going on.
Here is what I’ve found.
So up to and including 2013.1092 everything works fine for building my apps or the sample apps using my keystore.
From 2013.1093 onwards it fails to return the APK on both PC and Mac with the following output using the same keystore:
[exec] Result: 1
[exec] Result: 1
So I just tried building ‘Hello World’ sample app on 2013.1095 using the debug.keystore that I have had for a year and it built and returned the APK file.
Conclusion:
Using my own keystore I cannot build from 2013.1093 onwards on either PC or Mac, which also ties in with the daily build notes for 2013.1093 which are:
Mac/Windows: Added support for JDK 7
(32-bit/x86) to the Corona Simulator for Android builds. (This is used
to digitally sign APKs. Note that the 64-bit versions are not supported.
Corona Enterprise developers must still use 32-bit version of JDK 6,
which is an Android requirement.)
There is no doubt in my mind that this is where the problem lies.
I also wanted to point out that I have a password for my keystore alias as well so I need to input two passwords every build.
OK I believe I have found the issue.
@poon. Alex can you please confirm that you use 2 different passwords when building ie a keystore password and a key password please? As I am confident this is the issue as of 2013.1093.
Here is what I did to test.
Created a new test keystore file and put in my credentials, which has 2 passwords ie keystore password and key password, just like I did for my working keystore (up to 2013.1092)
Tried to build APK file (2013.1095) - FAILED
So created another keystore file with the same credentials and this time when it asks:
Enter key password for <xxxxxxxx>
(RETURN if same as keystore password):
I just pressed return so that they are the same password.
Tried to build APK file (2013.1095) - WORKED
Conclusion:
THere is something wrong as of 2013.1093 with the way Corona deals with our keystore files.
If you have a different kestore password and key password it will not return the APK file
If you have the same keystore password and key password it will Build and return the APK as expected.
I and some others cannot just go ahead and create new keysore files as it will mean that our previous apps will no longer be able to be updated.
Everything was working fine before Corona introduced in 2013.1093:
Mac/Windows: Added support for JDK 7
(32-bit/x86) to the Corona Simulator for Android builds. (This is used
to digitally sign APKs. Note that the 64-bit versions are not supported.
Corona Enterprise developers must still use 32-bit version of JDK 6,
which is an Android requirement.)
So there is a bug in the way Corona handles keystore files with a different keystore password and key password as of 2013.1093.
This is why it is only affecting a few people as I believe most will use the same keystore and key password.
Hopefully now you can get a fix out as soon as possible.
Everyone,
I was able to reproduce this issue yesterday on Windows and discovered it can happen if your “PATH” environment variable references a “jarsigner.exe” that is JDK 5 or an older version. Even though Corona finds the correct version of jarsigner on your system (we hunt it down when you open the Android build window via the registry), that environment variable is effectively overriding the version of jarsigner that we’re telling the build system to use. Also, Icy Spark is correct that this issue was introduced in daily build #1093, which is the version we added JDK 7 support. The settings we are passing into the jarsigner in that daily build are not supported by the JDK 5 or older jarsigner versions.
That said, we’ve developed a fix for this yesterday and we’ve successfully signed an APK using the JDK 5, 6, and 7 tools. We’ve also modified the Corona Simulator for Windows to ignore the “PATH” environment variable when doing an Android build to ensure that our build system uses the version of JDK tools expected. We’re performing the final tests now and plan on pushing out a new daily build this afternoon.