Hi!
I have a project developed with this version (2013.1076) but now I can’t build it, simulator shows “Could not connect to server. Please check your internet connection”.
Anyone knows if I can build my project with this version?
Thanks in advance
1076 is very old. We’ve had 12 public releases since then. With 100% certainty you cannot submit builds to Apple for iOS with a build that old. There may be a chance you could submit to Google Play, but the stores change requirements from time to time.
The current public build is 2906 and we would highly recommend you upgrade to a more modern version. At a minimum we need you to try and build a sample app with 2906 or later.
Also what operating system (and version) are you using?
Is there a reason you need to stay with that old of a build?
Also please make sure your system clock is correct.
Thanks
Rob
Hi, Rob!
My app is a abandomware that don’t runs in newer versions but I need build APK for my customer.
I work in Windows 10 (10.0.10586 N/D Comp. 10586) and the system clock is okay.
Thanks
Have you tried to use a more modern version with Graphics 1.0 compatibility turned on?
In your config.lua where you set the width/height add:
graphicsCompatibility = 1,
in with those and that will make Graphics 2.0 versions of Corona behave like old style apps.
Rob
Also make sure you can use Internet Explorer (not the new Windows browser) and try to sign into https://developer.coronalabs.com or see if you can find an XP machine and see if that changes your networking situation.
I’d tried in XP virtual machine and the same message. I suspect that I will not be able to build the app with this version :( 
Anyway it seems that the problem is in the connection simulator to build the package because the simulator itself does work perfectly.
The message appears when trying to connect to the servers.
Did you try connecting to https://developer.coronalabs.com with Internet Explorer? (not the new browser). Sometimes windows likes to put up a proxy that blocks connections. IE uses the same OS controls the simulator does to read the build servers, which is why the IE test is a good one.
Rob
What issues are you hitting if you try and build your app with a more modern version of Corona SDK? Have you tried the graphicsCompatibility mode 1 setting?
Rob
Hi, Rob!
Thanks for your time.
I connect to https://developer.coronalabs.com without problems (from IE, not Edge).
If I launch my project with the last Corona version with graphicsCompatibility=1 I obtain the next message:
That one is easy to fix. Go to: https://github.com/coronalabs/framework-sprite-legacy
Download the repo and copy the sprite.lua file from the repo folder to your project folder along side your main.lua. If you’re using Storyboard, you will have to do the same thing.
https://github.com/coronalabs/framework-storyboard-legacy
If you’re running 2830 or later, you should have a console window that opens with Corona. Those error messages will be in the console log and you may find it easier to copy/paste from a text window than having to make screencasts. Screen casts are great to see when thinks are not right on the screen or to make short videos demoing a problem, but for text based things like errors, copy/paste from that window is much better.
Rob
1076 is very old. We’ve had 12 public releases since then. With 100% certainty you cannot submit builds to Apple for iOS with a build that old. There may be a chance you could submit to Google Play, but the stores change requirements from time to time.
The current public build is 2906 and we would highly recommend you upgrade to a more modern version. At a minimum we need you to try and build a sample app with 2906 or later.
Also what operating system (and version) are you using?
Is there a reason you need to stay with that old of a build?
Also please make sure your system clock is correct.
Thanks
Rob
Hi, Rob!
My app is a abandomware that don’t runs in newer versions but I need build APK for my customer.
I work in Windows 10 (10.0.10586 N/D Comp. 10586) and the system clock is okay.
Thanks
Have you tried to use a more modern version with Graphics 1.0 compatibility turned on?
In your config.lua where you set the width/height add:
graphicsCompatibility = 1,
in with those and that will make Graphics 2.0 versions of Corona behave like old style apps.
Rob
Also make sure you can use Internet Explorer (not the new Windows browser) and try to sign into https://developer.coronalabs.com or see if you can find an XP machine and see if that changes your networking situation.
I’d tried in XP virtual machine and the same message. I suspect that I will not be able to build the app with this version :(
Anyway it seems that the problem is in the connection simulator to build the package because the simulator itself does work perfectly.
The message appears when trying to connect to the servers.
Did you try connecting to https://developer.coronalabs.com with Internet Explorer? (not the new browser). Sometimes windows likes to put up a proxy that blocks connections. IE uses the same OS controls the simulator does to read the build servers, which is why the IE test is a good one.
Rob
What issues are you hitting if you try and build your app with a more modern version of Corona SDK? Have you tried the graphicsCompatibility mode 1 setting?
Rob
Hi, Rob!
Thanks for your time.
I connect to https://developer.coronalabs.com without problems (from IE, not Edge).
If I launch my project with the last Corona version with graphicsCompatibility=1 I obtain the next message:
That one is easy to fix. Go to: https://github.com/coronalabs/framework-sprite-legacy
Download the repo and copy the sprite.lua file from the repo folder to your project folder along side your main.lua. If you’re using Storyboard, you will have to do the same thing.
https://github.com/coronalabs/framework-storyboard-legacy
If you’re running 2830 or later, you should have a console window that opens with Corona. Those error messages will be in the console log and you may find it easier to copy/paste from a text window than having to make screencasts. Screen casts are great to see when thinks are not right on the screen or to make short videos demoing a problem, but for text based things like errors, copy/paste from that window is much better.
Rob