I have a new Mac with Yosemite 10.10.1 and the terminal is not working. It doesn’t output anything, it just stays like this:
Any idea of what can be the problem? I don’t know what to look for certainly.
By the way, I used to view the logs in the “Console” app I can’t see them there as well.
Hi @luisherranz,
Which version of Corona SDK are you using? Since when did the console/Terminal reports stop showing? Did this occur only on upgrade to Yosemite, or when you upgraded Corona to a newer version? Are you using any IDEs like Glider or similar? Are you opening the Simulator through some unusual method like a command line script or something?
Thanks,
Brent
I am using the last public release and it is a new computer running 10.10.1 from the beginning.
I am not using any IDE, just Atom. I have tried opening Corona from the “Corona Simulator.app” in /Applications and running “open /Applications/CoronaSDK/Corona\ Simulator.app/” as well. Same result.
It works fine in my other Mac, running Yosemite as well.
What could I try?
If I open the /var/log/system.log file I can see there the last Corona Messages.
So, in some way, it is writing them there successfully, but they don’t appear in the terminal or the console.
Ok, deleting that file and restarting the syslogd did the trick 
simulator hangs when starting with the debugger icon app, the terminal and simulator open but simulator just hangs.
If starting with the corona icon app then simulator works but nothing is getting updated on the terminal window, just says
Corona Simulator Console
Diagnostics and Lua print output will appear here
Using version 2015.2511 on yosemite 10.10. Everything was working fine yesterday.
After re-installing corona and restarting my mac now i get
Dec 2 08:20:14.473: Logging binary sensor data to /var/folders/zz/zyxvpxvq6csfxvn_n00000sm00006d/C/locationdSensors.bin
Dec 2 08:20:14.476: NBB-Could not get UDID for stable refill timing, falling back on random
Dec 2 08:20:14.488: Location icon should now be in state ‘Inactive’
Dec 2 08:20:17.045: Couldn’t find a requirement string for masquerading client /System/Library/PrivateFrameworks/Parsec.framework
Dec 2 08:20:17.046: could not get apple languages array, assuming english
Dec 2 08:20:17.526: could not get apple languages array, assuming english
Dec 2 10:04:37.602: Couldn’t find a requirement string for masquerading client /System/Library/PrivateFrameworks/Parsec.framework
Dec 2 10:04:37.602: could not get apple languages array, assuming english
thanks this helped with same problem
Doesn’t help. I re-installed build 2014.2512 hoping this would help but still the same. If i launch from the corona icon the syslog window opens but just only shows info below, no further corona build info text nor debugging text. And if i launch from the debugger icon then the debugger window correctly shows the corona build info but the simulator then just hangs and can’t run any corona app.
Corona Simulator Console
Diagnostics and Lua print output will appear here
Looking in the Mac console it does correctly show the corona build text but I also see this line below, so not sure if it has anything to do with anything:
12/5/14 7:58:15.000 AM kernel[0]: Sandbox: Corona Simulator(775) System Policy: deny file-write-unlink /Users/admin/Library/Saved Application State/com.coronalabs.Corona_Simulator.savedState/restorecount.plist
Just for info, build 2014.2490 works perfectly when I launch from its core terminal icon.
Have you tried to run the Hello World sample app with 2511 and see if you get output there?
Rob
I am also having this same problem, any solution yet? Mine is still no t working properly.
I tried the /var/log/system.log everything is printing to that file, I deleted it and restarted, still nothing in the console.
I am running no other IDEs platform is Corona latest daily build on a Mac mini server with OS X Yosemite. I also tried re-installing Corona, rebooting, no change, as well as with the latest public release too.
Output problem is the same no matter what code I run in the simulator (including any of the example code that comes with Corona).
I recently installed the Android SDK and the output from Corona was working, even after the install of the Android SDK, but suddenly stopped outputting to the Corona Console last night.
Have you tried rebooting? Someone above suggested that restarting syslogd might be the cure.
Rob
Hi Rob,
Yes I rebooted a few times, no change. I can view the print output in my system console but still nothing on the Corona one.
Hi;
Now when I scroll up a page or so on the Corona Console I see this:
/Applications/CoronaSDK/Corona\ Simulator.app/Contents/Resources/console.sh ; exit;
Is it supposed to say the exit; part? It just outputs that when I start the simulator.
Basically the corona syslog no longer works for me (build 2014.2511,2512) so i have to rely on using the mac’s device console to see any of my debug text or errors, the syslog of corona never shows/updates anything. (it doesn’t even show the corona build details) And starting from the debugger icon simply hangs the simulator so that’s no use either.
The only one that still works properly with showing debug text is installing and launching with the corona terminal in build 2014.2490 but i don’t want to be using a very old version to build.
Very frustrating, for sure it has something to do with the mac’s system files not be properly updated or some path incorrectly set with the latest builds. When i first installed build 2014.2511 it did work for a while then there was one time I lost internet connection when running the simulator. After that it never worked again no matter how many times i have tried to re-install or reboot my mac.
Same thing here. The only way to see the logs right now is using the Console app.
I’ve reported this to Engineering. I’m wondering if something is causing syslogd to get confused. However it is the weekend, hopefully they will respond early this week.
Rob
@Rob, yes definitely that must be the case, when launching I can see the original terminal window pop up for a split second before closing and having only the syslog window remain on screen. Not sure if corona can do a double check or something that all paths are correct or something like that so the syslog doesn’t get confused.
Yes that is what is happening for me as well.
Cheers!
Thankfully, for some reason, the corona syslog has begun working again (build 2014.2511). Absolutely no idea why it does or does not as I didn’t make any changes on my Mac.