Terminal not working

Yep, that worked… Thanks!

No change whatsoever for the Simulator console. Corona Terminal works. Thanks :) 

When the trouble started, I noticed that the Corona Simulator app didn’t get activated last (so that I had to click on the Dock icon to be able to access its File menu. This had never been so before. Now that I start Corona Terminal, Corona Simulator is activated last again so that I don’t have to switch to it first.

When the Simulator starts, perhaps the console process is not (yet) available to attach to, and there is a problem with the code that checks that, perhaps related to behavior changed in Yosemite?

Im having the same problem… the console doesn’t work

Corona Simulator Console


Diagnostics and Lua print output will appear here

 

After the update i have to open the corona terminal manually  

 

What to do to solve this problem

I was using 2014.2511 on Yosemite 10.10.2, and it was working fine until a couple of days ago, now it’s not printing anything.

I updated to to 2015.2576, and it still doesn’t print anything. 

However, the Corona Terminal in the Corona SDK folder does work fine.

– Note –

Neither deleting the sys logs, nor restarting worked. I do see that when opening system.log with the console, and searching for ‘corona’ it does shows the prints.

Hi luisherranz, may I know which file you deleted and where to find syslogd to re-start? thanks a lot >.<

Hey Brent and Rob,

I just got this problem yesterday, where the log wasn’t printing to the terminal, 

Then today (this is purely for context, not a problem anymore), the app I work on hung before executing any of main.lua, would’t execute even a print on line 1, and no matter how many times I relaunched the app or uninstalled Corona it wouldn’t run in simulator. so I deleted its sandbox folder (that worked to un-hang the program).

I just decided to mention this strange thing because these problems were pretty much back to back.

======== Response to Questions from Rob Miracle======

What version of OS-X are you running? 10.10.2 OSX Yosemite

What version of Corona SDK are you running? Version 2014.2511 (2014.11.18)

Can you provide a screen shot showing the Corona Terminal that we started up? Yes, see below

Do you see your corona messages showing up in /var/log/system.log? Yes, see here

Andrews-Air-2:log georgepantazes$ cat system.log ... A bunch of stuff, then Apr &nbsp;9 15:10:49 Andrews-Air-2.attlocal.net Corona Simulator[1060]:&nbsp; Copyright (C) 2009-2014 &nbsp;C o r o n a &nbsp; L a b s &nbsp; I n c . Apr &nbsp;9 15:10:49 Andrews-Air-2.attlocal.net Corona Simulator[1060]: Version: 3.0.0 Apr &nbsp;9 15:10:49 Andrews-Air-2.attlocal.net Corona Simulator[1060]: Build: 2014.2511 Apr &nbsp;9 15:10:49 Andrews-Air-2.attlocal.net Corona Simulator[1060]: Platform: iPhone / x86\_64 / 10.10 / Intel HD Graphics 4000 OpenGL Engine / 2.1 INTEL-10.2.46 / 2014.2511 Apr &nbsp;9 15:10:49 Andrews-Air-2.attlocal.net Corona Simulator[1060]: The file sandbox for this project is located at the following folder: (/Users/georgepantazes/Library/Application Support/Corona Simulator/CORONA MyPlayground-ACBECA15B5750B5623A9487F9889B787) Apr &nbsp;9 15:10:49 Andrews-Air-2.attlocal.net Corona Simulator[1060]: WHATSUP Andrews-Air-2:log georgepantazes$&nbsp;

Are there any errors after Corona starts up? No

Do you see your corona messages showing up in the system Console app? Yes

Are there any errors after Corona starts up? No

When was the last time you rebooted your Mac? A few minutes ago in order to try to fix this problem.

Andrews-Air-2:log georgepantazes$ ls -l /var/log/system.log -rw-r-----@ 1 root &nbsp;admin &nbsp;62766 Apr &nbsp;9 15:09 /var/log/system.log Andrews-Air-2:log georgepantazes$ ps auxww | grep syslogd root &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 17 &nbsp; 0.0 &nbsp;0.0 &nbsp;2472956 &nbsp; 1104 &nbsp; ?? &nbsp;Us &nbsp; &nbsp;2:08PM &nbsp; 0:01.60 /usr/sbin/syslogd georgepantazes &nbsp; 1093 &nbsp; 0.0 &nbsp;0.0 &nbsp;2432772 &nbsp; &nbsp;628 s001 &nbsp;R+ &nbsp; &nbsp;3:10PM &nbsp; 0:00.00 grep syslogd Andrews-Air-2:log georgepantazes$&nbsp;

I’ve already tried deleting system.log and rebooting, but not restarting syslogd manually. As mentioned, we’ve already deleted the app Sandbox (not that that would have done anything). I’ve tried multiple different app projects.

Looking forward to your response! In the meantime, I will use Corona Terminal.