Build Error (Cannot login to build server)

Solar2D General Questions/Discussion
#21

I’m on Mac(s) - iMac and Macbook Air, versions. 2992 and 2952.  One of my developers is also unable to deauthorize their version, resulting in the same outcome (“connecting to server” hangs on screen, error message prints to console, application freezes, requires Force Quit).  My assumption is there’s an issue with the license server specific to authorization.  Unfortunately, this means I not only unable to build, but unable to develop at all.  

Is there any kind of server maintenance going on?  I’ve some issues building today as well, but those went away with on 2nd attempts.  

#22

I just did a Deauth and Quit and I was able to log back in. 

Could something have happened to your networking that would be routing you through a proxy? Usually we see the XMLRPC errors when a proxy gets turned on (Windows loves to do that, less common on Macs.)

I’ll ask engineering and see if they have any additional suggestions.

Rob

#23

Can I get your IP Address?

#24

71.167.186.164

#25

If you bring up Safari (has to be Safari) and hit this URL: https://developer.coronalabs.com/services/xmlrpc

What do you get?

Also can you run this command in the Terminal:

defaults write com.coronalabs.Corona\_Simulator debugWebServices 5

and then try to connect and post what you see in the console log?

Rob

#26

It seems to be working now - I’m able to authorize and build again!  I didn’t see any proxy on my connection, but I was doing a bunch of multiplayer testing today, so who knows what happened.  Reset the wifi and magically it all works again… either that or you waved a magic wand over my IP address :slight_smile:

Thanks for everything Rob - this community owes you a lot.  Happy to connect!

#27

Pasted that link in Safari and:

XML-RPC server accepts POST requests only.

 

Thanks again!

#28

Can’t build now, seems like https://developer.coronalabs.com/services/xmlrpc is not accessible.

Edit: Seems to be resolved now.

#29

This issue is back. Can’t build.

#30

Server is still down… I guess it’s still nighttime in California.

#31

That easier said than done. Only enterprise-builds can be done offline. Building using the Corona SDK (with simulator) still requires the Corona server, regardless if I have an Enterprise license. Combine that with a Windows-based development environment and there’s no business case for Enterprise.

#32

It seems to be working again (at least on my continent).

#33

I just did a few builds and it seems fine. If you’re having troubles please try again. Let me know if the problems continue.

Rob

#34

Just started having this issue in the last 20 minutes when trying to build for iOS. Have tried 2 different internet connections.

BUMP

#35

same for me

#36

I just tried to build for both iOS and Android and it was successful for me. Can you provide the error from your console log from the build?

Rob

#37

Rob,

Create Live Build throws the error #5 on 2017.3054

#38

Have you tried removing the .CoronaLiveBuild file?

Have you tried with a later daily build? 3068 is the new public build and it’s recommended that you upgrade to that version.

Are there error message in the Corona Console Log that could help us diagnose this?

Thanks

Rob

#39

Have upgraded to the latest daily/public 3068 and all issues are resolved, I didn’t spent too much time worrying about it (kept working on simulator acceptable tasks). Was too trying to do a live build for iOS, never tried normal builds. Was getting ERROR 11 initially then ERROR 5 and sometimes a generic time-out and cannot link app. Sorry logs are gone! All working now with latest build! :smiley:

Edit: Never tried any real TS measures, removing CoronaLive file etc

Edit: Was using Corona 3054

#40

( Have you tried removing the .CoronaLiveBuild file? )

This fixed it