Build issues with MAC OS X Vmware El Capitan 10.11.6

Solar2D General Questions/Discussion
#21

Something must have changed if you can no longer run something that used to work :slight_smile:

Try the last combination of VMWare, OS X, Xcode and CoronaSDK that worked for you.  If that doesn’t work then something you aren’t aware of must have changed (like a Windows update).  If it does, try with the latest version of CoronaSDK.  We haven’t changed anything that I know of that would affect things like this.

I assume you can build just fine using CoronaSDK installed natively on Windows 7 or you would have mentioned it.

#22

Something else you could try is to force a fresh login in the Simulator.

Exit the Corona Simulator and run this command (it will reset all of your Simulator preferences):

defaults delete com.coronalabs.Corona\_Simulator

then restart the Corona Simulator which will ask you to login.  Let us know if that works.

#23

Yes I can build fine on Windows 7.

VMware is the same, I updated from OSX 10.11.2 to 10.11.6 so could get Xcode 8 for iOS 10 SDK so can build for that. Needed the latest Corona version accordingly :frowning: Don’t think I can downgrade back to 10.11.2 without skipping iOS 10 as that is needed by my clients.

I did change my internet connection/new router as moved into new place and accidentally changed my VM mac address as well, but other things work fine. Just the call to the authorization servers keeps timing out.

Is there something else I can try to replicate the timeout ? A url or call etc, what kind of a call is the application making ?

Thanks

#24

The URL we asked you to visit in Safari earlier is that test.  If it still doesn’t work after reseting your preferences, PM me a _ complete _ copy of the Corona Console log from a failed session.

#25

That didn’t work, so let me run the failure scenario again and will send you the copy. Thanks

#26

While it runs as it takes a while to time out, can you confirm if bad provisioning profiles effect the build authorization step? 

#27

After trying a bunch of stuff, thanks to Perry finally identified the issue. The VM processors need to be 2, instead of 1 which I had set on my VM. Who would have thought :slight_smile:

Cheers guys, you are the best.