It is on a mac mini I just bought the other day so Its OS x 10.8.3 Server and xCode is also the latest version 4.6.2, thankyou Rob
And yes it does the same thing with the sample apps as well, I haven’t tried all of them but the ones I tired it just hangs.
I’m on a non-server version of Mac OS. Wonder it that makes a difference.
I have read a lot of docs and there isn’t any reference about the server version not being supported but I think I can change the startup to the non server version will try it and see.
I cant work it out, have submitted a support request…it sucks being noob 
Hmmm … this is an unusual one.
Here’s a stab in the dark: go to the www.coronalabs.com website and change your password and try to build again.
Ok I just tried the password change and the SDK asked me to re-enter the password on the mac and it accepted the password but still hangs during the build and never completes.
I am still having this issue and emailed support about it yesterday. I am just a pro user and it doesn’t look like I can get any email support included with my license is that right?
Peter
You are getting an error that is crashing the process and stopping the build process. I don’t know what is causing the fault. The engineers are aware that you are having this problem (and its not a common problem). They need time to figure out what is causing it. I understand you are quite frustrated by this as I would be.
I found a couple of older references to the specific error, but not much in the way of help solving it. One post suggested making sure to not use the team profile. Another seemed be based around not having the certificates right. You can read them here:
http://forums.coronalabs.com/topic/33711-certificate-not-installed-problem-when-build-for-device/
http://forums.coronalabs.com/topic/33548-my-app-not-build/
Most of the hits for that error have something to do with SQLite, but it sounds like that happens once the app is on device, or trying to access the Address book, but again, that would be on device and not during our build process.
Thanks
Rob
Thanks for the update Rob, I got a reply from support this morning and have sent them the crash log from Corona as requested I will have a read of those 2 threads.
Peter
Just for fun, download 1135, the new build that we released today and see if that makes any difference.
Downloading now, what is the best procedure for installing the latest build should I just delete the previous version or just install over the top? Macs have no registry so no uninstall program that I can find
Normally I just replace the folder. But in this case, I think I would delete the existing folder and empty the trash just to make sure.
ok deleted and installed the latest build and still the same issue, runs fine in the simulator on both Windows and Mac but the build just hangs, terminal window shows it stopping at the same point as previous versions…
Oh I hope I haven’t missed something really simple and I am going to be mortified
Time to start reaching for straws. Does your path to your main.lua have any non ASCII characters in it? What about spaces?
What about your certificate/key names? Provisioning Profiles?
Yes its in a folder on the desktop called “MCP Build Folder”
Should I post screen caps of the certificates and in here keys here?
Not necessary as long as you know they are clean names. Do you have a folder called “resources” in with your main.lua? Actually what all folders do you have in there?
Can you try to rename the folder and take the spaces out?
Your home folder doesn’t have any non-ASCII characters does it?
For issues like this, I recommend trying to build the HelloWorld sample app. It is a good place to start to determine if there is a general build problem.
Tom: I have tried some of the sample programs (not all of them) a couple of days ago with the same problem, will try the hello world app again shortly.
Rob: No resources folder I just have everything in one folder right now and just the usual chars on file names and home folder.
Peter
HelloWorld still hangs during build and I have to use the Activity Monitor to stop it.