Getting this classic build error as of this morning:
A device build error occurred on the server.
Error:
BuildID: 5702692ec9124
Hopefully the Corona crew is already working on a solution for this.
I’ve been getting a similar error for the past 15min or so…
"ERROR: An error occurred during build. The server returned the following message:
—
A device build error occurred on the server.
Error: Get plugin failed.
Publisher: com.coronalabs
Plugin: plugin.bit
BuildID: 57026bf5e3fc7"
No offence to Corona but this c*** needs to get fixed once and for all. I see this error posted every other day. Not angry or anything. Why does this error happen? Thanks!
For what it’s worth, it was working a few minutes later. Just wanted to make the issue known to the Corona team, but yeah, these things happen a little too frequently 
Ya I know. They don’t work and 2 min later start working. Why not just get it fixed and have it working allll the time?
@InfiSnyp. Welcome to the Internet. There are too many points of failure between a computer somewhere in the world and our servers. Sure our servers have hiccups from time to time. But so do the routers, switches and hubs that represent all of the nodes between us and you.
If build problems that were not happening start and it’s over 15 minutes, and you’ve verified that you can get to other sites, it’s worth dropping a post here. If we see multiple people having the issue that helps rule out a lot of network traffic. We have extensive monitoring on our servers (though I’m not set up to see it) and our engineers are quick to fix things.
Rob
Sorry if I sounded harsh. I totally understand hiccups. Doesn’t really give a problem to me because I know they will most likely be up in <10 min. I just go get a snack and get back and they are up! What if you made a pinned thread stating that they will come back on in just a little bit?
The issue just started happening again for me. Seems that it pops up every few weeks nowadays. Pretty poor really.
ERROR: Build Failed: A device build error occurred on the server.
Considering that this says ‘A device build error occurred on the server’ is would be fairly accurate to say that is is a server error on Coronas end.
Rob are you saying that this error might be mis-leading and instead pointing to a general network issue with the whole of the internet? If so could you advise how you arrived at this conclusion and what information you have to base this on?
If there is anything we can do to help fix this issue i.e run a specific debug build of Corona or something similar please advise as it would be advantageous to all going forward to get this resolved.
Why is it not possible to do offline builds? For basic users.
How did I arrive at the conclusion? I didn’t. It’s speculation based on the fact that your home ISP drops more than you think it does.
The build process runs mostly on your computer. Unlike a web page where you fetch it, read it for 5 minutes then fetch another, the build process is constantly sending data back and forth. We convert your .lua files into bytecode (compiled versions) and send them back. For plugins, we have to request each one and download it. If that process times out for any reason (our server down, our upstream provider hiccups, your upstream provider drops for a few seconds), then it’s possible that plugin download will fail and you get a build error.
We are working on improving messaging. However, these are all red herrings.
Transient errors are part of the system. One person reporting a problem of short duration is really hard for anyone to trouble shoot. In particular when it fixes itself. The likelihood that it’s a random problem outside of our control goes up. Now when multiple people report the problem and it’s going on for a while (15 minutes is an arbitrary target), then it points to a systemic problem on our end that we can actually look at and try to fix.
There is a base trouble shooting rule: Happens to one person? It’s a fluke. Happens to two people? Its a coincidence. Happens to three people? It’s a trend.
The gist of this is if it’s only happening to one person and everyone else is fine, it’s very likely a problem on your end and not ours. When multiple people are reporting it at the same time, then the likelihood that its our issue goes up. (regardless of what the error message says).
In the quest for us helping you, I go back to what I said above. If you’re still having build problems after 15 minutes and you’ve verified the network is fine on your side (You can get to Google, Windows hasn’t thrown a proxy up, etc). please report the issue here. If we see other reports, we can go poke the servers. If no one else is reporting it, then we can suggest additional local trouble shooting to try and see what the cause is.
Rob
Thank you for your response Rob. I think what the community is saying is that there is a systemic issue. Every thread that has been made for this error in the last few months has 5+ users replying of the EXACT same behaviour at the same time. Unfortunately I have wasted enough of my time on this error already, I hope going forward a permanent solution can be found so we can build without this persistent error message as has been the case for the last 2+ years prior to Febuary. (since I have been using Corona SDK)
Simon
I’ve been getting a similar error for the past 15min or so…
"ERROR: An error occurred during build. The server returned the following message:
—
A device build error occurred on the server.
Error: Get plugin failed.
Publisher: com.coronalabs
Plugin: plugin.bit
BuildID: 57026bf5e3fc7"
No offence to Corona but this c*** needs to get fixed once and for all. I see this error posted every other day. Not angry or anything. Why does this error happen? Thanks!
For what it’s worth, it was working a few minutes later. Just wanted to make the issue known to the Corona team, but yeah, these things happen a little too frequently
Ya I know. They don’t work and 2 min later start working. Why not just get it fixed and have it working allll the time?
@InfiSnyp. Welcome to the Internet. There are too many points of failure between a computer somewhere in the world and our servers. Sure our servers have hiccups from time to time. But so do the routers, switches and hubs that represent all of the nodes between us and you.
If build problems that were not happening start and it’s over 15 minutes, and you’ve verified that you can get to other sites, it’s worth dropping a post here. If we see multiple people having the issue that helps rule out a lot of network traffic. We have extensive monitoring on our servers (though I’m not set up to see it) and our engineers are quick to fix things.
Rob
Sorry if I sounded harsh. I totally understand hiccups. Doesn’t really give a problem to me because I know they will most likely be up in <10 min. I just go get a snack and get back and they are up! What if you made a pinned thread stating that they will come back on in just a little bit?
The issue just started happening again for me. Seems that it pops up every few weeks nowadays. Pretty poor really.
ERROR: Build Failed: A device build error occurred on the server.
Considering that this says ‘A device build error occurred on the server’ is would be fairly accurate to say that is is a server error on Coronas end.
Rob are you saying that this error might be mis-leading and instead pointing to a general network issue with the whole of the internet? If so could you advise how you arrived at this conclusion and what information you have to base this on?
If there is anything we can do to help fix this issue i.e run a specific debug build of Corona or something similar please advise as it would be advantageous to all going forward to get this resolved.
Why is it not possible to do offline builds? For basic users.
How did I arrive at the conclusion? I didn’t. It’s speculation based on the fact that your home ISP drops more than you think it does.
The build process runs mostly on your computer. Unlike a web page where you fetch it, read it for 5 minutes then fetch another, the build process is constantly sending data back and forth. We convert your .lua files into bytecode (compiled versions) and send them back. For plugins, we have to request each one and download it. If that process times out for any reason (our server down, our upstream provider hiccups, your upstream provider drops for a few seconds), then it’s possible that plugin download will fail and you get a build error.
We are working on improving messaging. However, these are all red herrings.
Transient errors are part of the system. One person reporting a problem of short duration is really hard for anyone to trouble shoot. In particular when it fixes itself. The likelihood that it’s a random problem outside of our control goes up. Now when multiple people report the problem and it’s going on for a while (15 minutes is an arbitrary target), then it points to a systemic problem on our end that we can actually look at and try to fix.
There is a base trouble shooting rule: Happens to one person? It’s a fluke. Happens to two people? Its a coincidence. Happens to three people? It’s a trend.
The gist of this is if it’s only happening to one person and everyone else is fine, it’s very likely a problem on your end and not ours. When multiple people are reporting it at the same time, then the likelihood that its our issue goes up. (regardless of what the error message says).
In the quest for us helping you, I go back to what I said above. If you’re still having build problems after 15 minutes and you’ve verified the network is fine on your side (You can get to Google, Windows hasn’t thrown a proxy up, etc). please report the issue here. If we see other reports, we can go poke the servers. If no one else is reporting it, then we can suggest additional local trouble shooting to try and see what the cause is.
Rob