Android build failed (5)

BuildID: kCoronaBuild [A device build error occurred on the server.

BuildID: 563c0c9935bab

Error: Template not found.

Build Number: 2015.2731

Platform: android

Platform Version: 2.2

Template Type: basic

ERROR: An error occurred during build. The server returned the following message

:


A device build error occurred on the server.

BuildID: 563c0c9935bab

Error: Template not found.

Build Number: 2015.2731

Platform: android

Platform Version: 2.2

Template Type: basic


Android build failed (5)

Here’s mine:
 

BuildID: kCoronaBuild [A device build error occurred on the server.

BuildID: 563c1176497c1

Error: Template not found.

Build Number: 2015.2731

Platform: android

Platform Version: 2.2

Template Type: basic

ERROR: An error occurred during build. The server returned the following message:


A device build error occurred on the server.

BuildID: 563c1176497c1

Error: Template not found.

Build Number: 2015.2731

Platform: android

Platform Version: 2.2

Template Type: basic


Android build failed (5)

At least we’re suffering together, Lorz :slight_smile:

Uninstalling Corona and re-installing with lots of restarts, etc does nothing to fix this.  Is there a guide for completely wiping out any traces of Corona from a Windows machine, beyond the uninstaller?

This is likely not an installation problem. It’s likely a networking problem.

Can you use Internet Explorer and access http://developer.coronalabs.com ? You have to use IE, not Chrome or Firefox.

Mine has worked today :slight_smile:

Hi Rob, thanks for the reply.

Yes I can get there fine with IE.  What am I looking for?

I still have this issue :frowning:

Well this error is network connectivity. If you’re being routed through a proxy (which Windows loves to setup for you), or you’re having connectivity issues, then these problems will show up.

You’re loading quite a few plugins and some are pretty big.  I would first suggest trying to build our Hello World sample and see if you’re having the error. After that, look to see if you really need all those plugins. You can try using a different  internet connection (if you have a laptop, go to a coffee shop).

Rob

So if I install 2100 I can build successfully again.  But anything modern I can’t.  

I used a laptop with 2731 and it worked, so at least I have workaround.  Still, kind of a pain my primary development machine can no longer use any modern Corona versions :expressionless:

Sadly we need all those plugins for ad mediation.  

Well likely one of the plugins is the cause, I would suggest starting with the 3rd party ones like Chartboost. Ingemar has recently stopped support this plugin and it has probably fallen out of compliance with current build requirements. You are with 100% certainty not going to be able to deploy to Apple iOS devices with build 2100. You also will not be able to use AdMob with that old of a build too.

Start commenting out plugins until you identify the culprit.

Rob

This problem is repeatable.  On any machine where building is working, uninstall Corona and install Corona 2100 (last build that supports Samsung releases).  Do a build.  Now uninstall 2100 and re-install latest version.  Builds no longer work.

But good news for anyone having this problem, we found a fix:

  1. Install anything that gives you a drop down for the google version like (CoronaSDK-2015.2659)

  2. Build any game you want (this will flush the 2.2 version setting corona holds somewhere)

  3. Install the latest version of Corona again and you’re all set. 

Hope this helps!

That bug should have been fixed in CoronaSDK 2015.2741:

Windows - Fix targeting of old OS releases (using a very old build could cause new builds to choose wrong Android version) - no casenum

Can you confirm which version you were seeing the problem in?  2731 was mentioned earlier which would have had it but you later mention using the “latest version of Corona” which is confusing.

The latest we used was 2731, and one version older than that.

That bug you quoted seems to be exactly what we were experiencing!  Once we used the very old 2100 (for Samsung) we were stuck building for 2.2 on that machine if we updated back to 2731.  

Great to knew a fix is already in, thanks.