Terminal not working

[henrik5]

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?

[BK_PANARA]

I found a very simple temporary solution for now.

1. open corona simulator 
2. open var/log/ 
3. open system.log file in TextWrangler
4. Run any project

You can see all the log in the open system.log file (as per luisherranz ) and we can consider TextWrangler as corona terminal  ;)  

I know this is not permanent solution but we can go on for now until CORONA finds the solution. 

Please Corona solve this ASAP.

Thank you.
Bhavin 
 

[rob]

Update:  This still seems to be a system by system issue.  Many people are using the new console setup with great success.  Here is a list of information that will help us:

What version of OS-X are you running?

What version of Corona SDK are you running?

Can you provide a screen shot showing the Corona Terminal that we started up?

Do you see your corona messages showing up in /var/log/system.log?  Are there any errors after Corona starts up?

Do you see your corona messages showing up in the system Console app?  (Spotlight search, type in Console)  Are there any errors after Corona starts up?

When was the last time you rebooted your Mac?

While we work to solve this, we will be adding a version of “Corona Terminal” back into the .dmg package for those who are worried about doing any command line work.  We will be posting a version of it later that you can add for those without access to Daily Builds.

Rob

[BK_PANARA]

My terminal started working again  :) 

Don’t know how… :o 

I am using build 2014.2521.

Bhavin 

[Supertapp]

Mine has stopped working today after shutting my mac down last night and rebooting as normal this morning 

To answer your questions Rob:

Yosemite 10.10.1

Corona 2511 (however 2524 behaves the same)

http://imageshack.com/a/img537/7826/onp2c6.png

Yes

No

Yes

No

This morning (8am GMT)

Oh dear, please get the old style one back in a daily build ASAP!!

[rob]

Daily build 2526 has “Corona Terminal” back that you can use to launch Corona SDK and get output to the terminal window liked it used to be until we can figure out what’s going on with syslogd.

Rob

[BK_PANARA]

Thanks Rob.

That’s really much better for those whose terminal is still not working or again stop working.

Thanks you For very quick update.

Bhavin 

[xming0529]

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

[arianmaps]

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.

[stone_hkhk]

@luisherranz

Ok, deleting that file and restarting the syslogd did the trick 

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

[georgeinspector]

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  9 15:10:49 Andrews-Air-2.attlocal.net Corona Simulator[1060]:  Copyright (C) 2009-2014  C o r o n a   L a b s   I n c . Apr  9 15:10:49 Andrews-Air-2.attlocal.net Corona Simulator[1060]: Version: 3.0.0 Apr  9 15:10:49 Andrews-Air-2.attlocal.net Corona Simulator[1060]: Build: 2014.2511 Apr  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  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  9 15:10:49 Andrews-Air-2.attlocal.net Corona Simulator[1060]: WHATSUP Andrews-Air-2:log georgepantazes$ 

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  admin  62766 Apr  9 15:09 /var/log/system.log Andrews-Air-2:log georgepantazes$ ps auxww | grep syslogd root               17   0.0  0.0  2472956   1104   ??  Us    2:08PM   0:01.60 /usr/sbin/syslogd georgepantazes   1093   0.0  0.0  2432772    628 s001  R+    3:10PM   0:00.00 grep syslogd Andrews-Air-2:log georgepantazes$ 

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.

[rickyd1]

I have/had this issue with the latest build (Version 2014.2511 (2014.11.18)). I am on OSX 10.10.2. The only incidents in the past week was I had to force restart and I recently ran system updates. Not sure if either had a role in breaking the connection.  

I tried to delete the log file but that did not help. However, I found a work around.

Trying to open the application from Launchpad or from the Applications folder, opens the app but does not print the data to terminal. 

Solution

1. Go to Applications >CoronaSDK > Corona Simulator and right click. You should see a menu. Click Show package contents
2. Navigate to and open Contents > MacOS > Corona Simulator 

Terminal will open with two windows. The front one will say 

Corona Simulator Console ------------------------ Diagnostics and Lua print output will appear here

but nothing will ever print to it. Close that…

The back one will say something like

/Applications/CoronaSDK/Corona\ Simulator.app/Contents/MacOS/Corona\ Simulator ; exit; 2015-02-06 17:31:13.996 Corona Simulator[848:538617]  Copyright (C) 2009-2014  C o r o n a   L a b s   I n c . 2015-02-06 17:31:13.996 Corona Simulator[848:538617] Version: 3.0.0 2015-02-06 17:31:13.996 Corona Simulator[848:538617] Build: 2014.2511

This window will print. 

Not sure if this will help anyone else, but it has helped me.

[Divergent_Monkey]

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?

[rob]

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

[Divergent_Monkey]

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?

[bjsorrentino]

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

[rob]

What version of Corona SDK are you running?

[henrik5]

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:

1. Set permissions for all groups to r/w for /var/log/system.log

2. restart syslogd

• Didn’t work.

3. Delete system.log

4. restart syslogd

• Didn’t work. Got the simulator blah blah sh ; exit message above, though

5. 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.

6. 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.

[Divergent_Monkey]

@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]_

[rob]

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