Same here 2500, 2511, 2517 no print outs on yosemite 10.10.1 
Please fix this as its a real PITA although the workaround is to use console for now!
I found build 2014.2494 prints out to the terminal which is nice but do we have any info on what the score is with the newer builds doing so??
My /var/log/system.log file contains all the print out data but deleting it and restarting doesn’t fix the issue
I’m using build 2500 and syslog is working but hogs 99% cpu, it’s a pain in the ass as every new window creates another syslog and starts spinning the fans in my macbook like crazy. I restarted my machine and the syslog pops up and then disappears after I close the corona simulator, so I guess I had it going on for too long and this problem persisted until I restarted the machine
Mine randomly started working again yesterday :huh:
Hi Rob,
I am using daily build 2014.2521 , I also have terminal issue and try the tricks to delete system.log file but not works for me.
I tried your commands and get this output
Bhavins-Mac-mini:~ BKPANARA$ ps auxww | grep syslogd
BKPANARA 708 0.3 0.0 2423356 200 s001 R+ 7:13PM 0:00.00 grep syslogd
root 17 0.0 0.0 2474004 1548 ?? Ss 6:40PM 0:00.95 /usr/sbin/syslogd
Please guide me , what should i do for terminal working.
Thank You.
Bhavin
I’m having the same problem…
The workaround provided by rickyd1 works nicely but it is still a drag. I think these problems started when I updated from Yosemite 10.10.1 to 10.10.2. I’m using Corona 2014.2511. My syslog says:
25/02/15 22:19:31,442 Corona Simulator[2007]:
Copyright © 2009-2014 C o r o n a L a b s I n c .
25/02/15 22:19:31,442 Corona Simulator[2007]: Version: 3.0.0
25/02/15 22:19:31,442 Corona Simulator[2007]: Build: 2014.2511
I read that this problem magically disappeared for some of you. That is not the case for me although I have even tried sitting on the floor with my macbook inside a pentagram painted in goat blood while chanting old Mayan songs…
@Rob: any news on this issue?
Hi, mine started working again randomly, didn’t do anything different it just started working again. I tried everything suggested an nothing then suddenly it works again.
I did uninstall the Android SDK and re-install it? Don’t know if that did it or what?
Cheers and good luck guys!
There should be an option called “Corona Terminal” in the folder with Corona Simulator. Run that and see if you can see your messages.
Rob
In my folder /Applications/CoronaSDK/ there is no such file. The only files there are the simulator, debugger, documentation.html and two libraries (in which I cannot find “Corona Terminal” either). Have I misunderstood you?
Hi @coronarocks,
When you open “Corona Simulator” it should automatically open up the OS X Terminal which shows your Corona “console debugging” output. Is this simply not occurring?
Brent
What version of Corona SDK are you running?
Got this yesterday. I associated it with having to force quit Corona because the build process hung. But I don’t remember if logging got affected right away, since I was building for device and debugging in the XCode device console at the time. So consider it no data.
I’ve taken the following steps:
-
Set permissions for all groups to r/w for /var/log/system.log
-
restart syslogd
- Didn’t work.
-
Delete system.log
-
restart syslogd
- Didn’t work. Got the simulator blah blah sh ; exit message above, though
- Re-download and reinstall Corona SDK 2014.2511.
- Didn’t work. Got the below output from the setting “auto-open last project”, delayed by 14 seconds or so. Strange. After that, adding a print(“hello”) and Ctrl+r does not show those messages, or the hello.
- Remembered that I’d changed some settings in Corona preferences yesterday and changed them back to the default.
- Didn’t work. Same delayed console init-messages and no print output.
It seems it gets in some “mode”. Damaged plist files have caused trouble for another app, does the Corona Simulator have any that should be deleted and re-generated?
Corona Simulator Console
Diagnostics and Lua print output will appear here
Feb 27 15:26:36.491:
Copyright © 2009-2014 C o r o n a L a b s I n c .
Feb 27 15:26:36.491: Version: 3.0.0
Feb 27 15:26:36.491: Build: 2014.2511
Feb 27 15:26:46.516:
Copyright © 2009-2014 C o r o n a L a b s I n c .
Feb 27 15:26:46.516: Version: 3.0.0
Feb 27 15:26:46.517: Build: 2014.2511
Feb 27 15:26:46.538: Platform: iPhone / x86_64 / 10.10 / ATI Radeon HD 4670 OpenGL Engine / 2.1 ATI-10.0.19 / 2014.2511
Feb 27 15:26:46.595: The file sandbox for this project is located at the following folder:
(/Users/henrikerlandsson/Library/Application Support/Corona Simulator/Moon Phase-CB79D3982EB1768DE263E298C3A43597)
Feb 27 15:26:47.747: background and statusbar set. height vs 320 width: 480
Starting the debugger instead (There is no such thing as Corona Terminal in my Applications Directory Rob - there used to be in previous versions) gives two console windows:
One titled "<my user> - Corona Simulator Console - syslog (not syslogd, if that matters). Before opening any app, prints (printing delayed by 4 seconds or so):
Corona Simulator Console
Diagnostics and Lua print output will appear here
Feb 27 15:55:12.879:
Copyright © 2009-2014 C o r o n a L a b s I n c .
Feb 27 15:55:12.879: Version: 3.0.0
Feb 27 15:55:12.879: Build: 2014.2511
Terminal window #2 is entitled “<my user> - debugger - debugger” and contains:
Last login: Fri Feb 27 15:54:34 on ttys000
________________________________________[~]________________________________________
> /Applications/CoronaSDK/debugger ; exit;
DEBUGGER: Corona Remote Debugger
DEBUGGER: Go to the Simulator and run the program you wish to debug
2015-02-27 15:55:12.879 Corona Simulator[38309:227798]
Copyright © 2009-2014 C o r o n a L a b s I n c .
2015-02-27 15:55:12.879 Corona Simulator[38309:227798] Version: 3.0.0
2015-02-27 15:55:12.879 Corona Simulator[38309:227798] Build: 2014.2511
Starting the app adds the usual sandbox info (so the first terminal quote should be how it should look, no problem) and typing run produces the expected print statements I added for testing - in the debugger window, but NOT in the Corona Simulator Console. Ctrl+r terminates the app and it seems it’s made so you have to quit and restart the debugger to run it again?
So now I want to restart syslogd AND syslog. Is that safe? I’ll also try a clean reinstall of Corona, if all that’s required is to delete the files in Applications and installing it again.
@Rob: version 2014.2511
@Brent: the window opens with the content below. However, no output from my app is displayed.
_Corona Simulator Console
Diagnostics and Lua print output will appear here
Feb 27 21:15:31.089: Platform: iPad / x86_64 / 10.10 / Intel Iris OpenGL Engine / 2.1 INTEL-10.2.46 / 2014.2511
Feb 27 21:15:31.222: The file sandbox for this project is located at the following folder: [my sandbox folder]_
I would recommend updating to the beta version with 64 bit support. You need this version to deploy to Apple anyway. See:
http://coronalabs.com/blog/2015/01/21/update-on-corona-ios-64-bit-support-and-plugins/
This should contain a “Corona Terminal” that you can use if the auto-start console doesn’t work for you.
Rob
Same problem here, older version of Corona that came with the corona terminal in the folder, works.
Should be something that changed after fuse powered.
I keep getting the notifications for this post updating…
When mine wasn’t working for someone who develops full time in Corona this was a BIG inconvenience, fortunately as I mentioned mine started working randomly by itself.
However if it had not started working I find the radio silence from the Corona staff on this issue very disheartening for what seems to be a common problem.
Come on guys sort it out!!
Yep, that worked… Thanks!
Engineering is looking into it. We can’t reproduce it. It’s working fine on our computers. This isn’t something that a bug report will help with either. In the mean time…
This is a change to make the Mac version of Corona SDK behave like Windows with regards to starting up an output window for you. On OSX prior to this change, you had to launch “Corona Terminal” to get an output window. It would then start Corona Simulator for you. On Windows, you just launch Corona Simulator and we start a command shell for you. This is the desirable behavior instead of having the Corona Terminal method of launching. It seems some people’s syslogd/logfiles are not behaving the same as they are on other Macs.
In the mean time, if you want to go back to having a “Corona Terminal” and launch it old school like, go to this thread:
http://forums.coronalabs.com/topic/52629-new-mac-console-loving-it/page-2
Scroll down my Dec 2. post and implement the script there and see if it helps you until we can sort this out.
Rob
I only get syslog output when building a project from Sublime. Running the simulator by itself and opeing a project I get no syslog output.
I usually immediately close it, (I have a terminal feedback in sublime) because it’s just eating away CPU like mad.
Is it just me or those the syslog take 95% of the cpu when it’s running. I don’t recall this being a big issue or maybe I never noticed it, but it’s downright annoying on a laptop.
This is all the latest build on Yosemite. Anyway to disable terminal on Corona Startup??? I
No change whatsoever for the Simulator console. Corona Terminal works. Thanks :)