You should be able todo OPTION-COMMAND-Escape and bring up a list of running apps and kill non-responding apps.
I’m not sure why it hung. Builds should be under a minute or so in most cases.
You should be able todo OPTION-COMMAND-Escape and bring up a list of running apps and kill non-responding apps.
I’m not sure why it hung. Builds should be under a minute or so in most cases.
Can you build on your PC?
Thanks for the reply Ksan, I haven’t tried building on the PC for Android as I need it working on iOS first…
Thanks for the reply Rob, can you see anything from your side? Where can I look for an error message or a log?
Hi @pk6. I can’t see anything on my side. Only certain engineers have access to that data. If you’re on a Mac you should be starting Corona using the “corona-terminal” app in /Applications/CoronaSDK. This will open a terminal window, which then starts up Corona SDK. Messages from Corona end up in that terminal window.
Ok thanks Rob, I will try that.
I just purchased Corona thinking that the latest build might solve the problem but it didn’t 
I opened the terminal window during the build and it still hangs but here is the terminal window output:
Copyright © 2009-2013 C o r o n a L a b s I n c .
2013-06-03 08:36:50.285 Corona Simulator[300:707] Version: 2.0.0
2013-06-03 08:36:50.285 Corona Simulator[300:707] Build: 2013.1134
2013-06-03 08:36:50.287 Corona Simulator[300:707] The file sandbox for this project is located at the following folder:
(/Users/Peter/Library/Application Support/Corona Simulator/MCP Build Folder-FE55F6223D6993A2EACDE452BF34693A)
2013-06-03 08:36:50.749 Corona Simulator[300:707] WARNING: Simulator does not support multitouch events
2013-06-03 08:37:17.099 Corona Simulator[300:707] Using Custom Build Id c37d18cfe79e3679aa32a78d432c845e
2013-06-03 08:37:17.178 Corona Simulator[300:707] *** -[NSPlaceholderString initWithUTF8String:]: NULL cString
2013-06-03 08:37:17.179 Corona Simulator[300:707] (
0 CoreFoundation 0x00007fff8d1c0b06 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff90bf83f0 objc_exception_throw + 43
2 CoreFoundation 0x00007fff8d1c08dc +[NSException raise:format:] + 204
3 Foundation 0x00007fff88f5693c -[NSString initWithUTF8String:] + 74
4 Corona Simulator 0x000000010002ec0e start + 183182
5 Corona Simulator 0x000000010002e933 start + 182451
6 Corona Simulator 0x0000000100029d4a start + 163018
7 Corona Simulator 0x000000010002a8e6 start + 165990
8 Corona Simulator 0x000000010001511b start + 77979
9 Corona Simulator 0x000000010000de5f start + 48607
10 Foundation 0x00007fff88f24395 __NSFireDelayedPerform + 358
11 CoreFoundation 0x00007fff8d17d804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
12 CoreFoundation 0x00007fff8d17d31d __CFRunLoopDoTimer + 557
13 CoreFoundation 0x00007fff8d162ad9 __CFRunLoopRun + 1529
14 CoreFoundation 0x00007fff8d1620e2 CFRunLoopRunSpecific + 290
15 HIToolbox 0x00007fff90878eb4 RunCurrentEventLoopInMode + 209
16 HIToolbox 0x00007fff90878c52 ReceiveNextEventCommon + 356
17 HIToolbox 0x00007fff90878ae3 BlockUntilNextEventMatchingListInMode + 62
18 AppKit 0x00007fff91f03563 _DPSNextEvent + 685
19 AppKit 0x00007fff91f02e22 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
20 AppKit 0x00007fff91efa1d3 -[NSApplication run] + 517
21 AppKit 0x00007fff91e9ec06 NSApplicationMain + 869
22 Corona Simulator 0x00000001000020b4 start + 52
23 ??? 0x0000000000000001 0x0 + 1
)
I cant see any obvious error message but hopefully someone else can?
Peter
Before I send this to the engineers, what version of OS-X is this happening on and what version of XCode do you have installed?
Also does this happen if you try and build one of our Sample apps?
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 