Build Error #1 with only one of our signing keys after updating to latest public release

Hi folks, after updating to the latest public release we are getting “Build Error #1” failures when building for Android.  I’ve also tried using the latest daily build with the same error.

The build is sent to Corona, it takes several minutes while Corona builds it, the console says it is starting to download after getting a BuildID and then it fails.

Note this only happens with ONE of our signing keys.  I can build the game successfully with one of our Production keys, but our other Production key encounters problems.  Half our portfolio uses one key, the other half uses the other key.  So right now we can’t update half our portfolio on Android and we have critical security patches to rollout before Jan 15 or our Google Play account will be suspended.

Things we have tried:

  1. Turning debugging on in registry.  See results below.

  2. Changing Java versions to latest as recommended by Corona.

  3. Trying the keys on different computers - same results (one key works, the other doesn’t).

  4. Trying different versions of Corona SDK, including latest daily and public builds.

Here’s the output with the key that fails:

10:34:49.598  Testing credentials for ‘X:\Dropbox_FireRabbit - Administration\Keys\AlexFireRabbit.keystore’: 

10:34:50.229  Picked up JAVA_TOOL_OPTIONS: -Duser.language=en

10:34:50.239  WebServices: Call: system.connect 

10:34:50.642  WebServices: Response received in 0 seconds

10:34:50.642  WebServices: Call: corona.getTime 

10:34:51.037  WebServices: Response received in 1 seconds

10:34:51.037  WebServices: Call: user.login2 

10:34:51.628  WebServices: Response received in 0 seconds

10:34:51.638  Excluding specified files from build: 

10:34:51.638     excluding: *.ogg

10:34:51.638     excluding: Launch.png

10:34:51.638     excluding: Launch@2x.png

10:34:51.638     excluding: Launch@3x.png

10:34:51.638     excluding: FireRabbitLaunchScreen.storyboardc

10:34:51.638     excluding: Images.xcassets

10:34:51.638     excluding: Icon-40.png

10:34:51.638     excluding: Icon-58.png

10:34:51.638     excluding: Icon-76.png

10:34:51.638     excluding: Icon-80.png

10:34:51.638     excluding: Icon-87.png

10:34:51.638     excluding: Icon-120.png

10:34:51.638     excluding: Icon-152.png

10:34:51.638     excluding: Icon-167.png

10:34:51.638     excluding: Icon-180.png

10:34:51.638     excluding: Icon-1024.png

10:34:51.638     excluding: carnageflexibles/horseHUD*

10:34:51.638     excluding: carnageflexibles/swinventory*

10:34:52.345  WebServices: Call: corona.build.7 

10:36:25.434  WebServices: Response received in 93 seconds

10:36:25.434  BuildID: 5a538f9b3c450

10:36:25.434  WebServices: Call: corona.getUrl 

10:36:25.875  WebServices: Response received in 0 seconds

10:36:25.875  WebServices: downloading build

10:36:27.925  WebServices: Download of 9805516 bytes complete in 2 seconds (4.68MB/s)

10:36:38.614  Android build failed (1) after 107 seconds

10:36:38.614  WebServices: Call: user.logout 

10:36:39.089  WebServices: Response received in 1 seconds

Here’s the output of the exact same build, 11 minutes later, with the key that works:

10:47:58.266  Testing credentials for ‘X:\Dropbox_FireRabbit - Administration\Keys\EndersLock.keystore’: 

10:47:58.955  Picked up JAVA_TOOL_OPTIONS: -Duser.language=en

10:47:58.988  WebServices: Call: system.connect 

10:47:59.426  WebServices: Response received in 1 seconds

10:47:59.426  WebServices: Call: corona.getTime 

10:47:59.867  WebServices: Response received in 0 seconds

10:47:59.867  WebServices: Call: user.login2 

10:48:00.424  WebServices: Response received in 1 seconds

10:48:00.435  Excluding specified files from build: 

10:48:00.435     excluding: *.ogg

10:48:00.435     excluding: Launch.png

10:48:00.435     excluding: Launch@2x.png

10:48:00.435     excluding: Launch@3x.png

10:48:00.435     excluding: FireRabbitLaunchScreen.storyboardc

10:48:00.435     excluding: Images.xcassets

10:48:00.435     excluding: Icon-40.png

10:48:00.435     excluding: Icon-58.png

10:48:00.435     excluding: Icon-76.png

10:48:00.435     excluding: Icon-80.png

10:48:00.435     excluding: Icon-87.png

10:48:00.435     excluding: Icon-120.png

10:48:00.435     excluding: Icon-152.png

10:48:00.435     excluding: Icon-167.png

10:48:00.435     excluding: Icon-180.png

10:48:00.435     excluding: Icon-1024.png

10:48:00.435     excluding: carnageflexibles/horseHUD*

10:48:00.435     excluding: carnageflexibles/swinventory*

10:48:01.152  WebServices: Call: corona.build.7 

10:50:01.391  WebServices: Response received in 120 seconds

10:50:01.391  BuildID: 5a5392b03a716

10:50:01.391  WebServices: Call: corona.getUrl 

10:50:01.888  WebServices: Response received in 0 seconds

10:50:01.888  WebServices: downloading build

10:50:04.425  WebServices: Download of 9805513 bytes complete in 3 seconds (3.12MB/s)

10:50:17.768  Android build succeeded in 137 seconds

10:50:17.768  WebServices: Call: user.logout 

10:50:18.200  WebServices: Response received in 1 seconds

Please help :slight_smile:

When you say “latest daily build” or “latest public build”, please be specific on the version… 2017.xxxx or 2018.xxxx (and we need the .xxxx values)

Are you building from Windows? 

What version of the Java JDK do you have installed? 

Have you read this thread:  and tried some of its remedies?

Rob

Hi Rob, thanks for the quick response.

We’ve tried:
2017.3184
2018.3194

Building from Windows.

One machine has JDK 7.0.8, another had JDK 8u151.  

Both machines have same results: one key works and has always worked, the second key has stopped working after upgrading to the two Corona builds above.

You didn’t link anything in your reply, can you try again?

Cheers,

Chris

Oops sorry: https://forums.coronalabs.com/topic/71172-android-build-failed-1/

Rob

Thank Rob. I figured it is likely best we continue to the conversation the sub thread you pointed us in below:
https://forums.coronalabs.com/topic/71138-build-fail-without-error-code/page-2

Hope that works for you…

Thanks!

When you say “latest daily build” or “latest public build”, please be specific on the version… 2017.xxxx or 2018.xxxx (and we need the .xxxx values)

Are you building from Windows? 

What version of the Java JDK do you have installed? 

Have you read this thread:  and tried some of its remedies?

Rob

Hi Rob, thanks for the quick response.

We’ve tried:
2017.3184
2018.3194

Building from Windows.

One machine has JDK 7.0.8, another had JDK 8u151.  

Both machines have same results: one key works and has always worked, the second key has stopped working after upgrading to the two Corona builds above.

You didn’t link anything in your reply, can you try again?

Cheers,

Chris

Oops sorry: https://forums.coronalabs.com/topic/71172-android-build-failed-1/

Rob

Thank Rob. I figured it is likely best we continue to the conversation the sub thread you pointed us in below:
https://forums.coronalabs.com/topic/71138-build-fail-without-error-code/page-2

Hope that works for you…

Thanks!