can’t open console.sh

Solar2D Daily Builds and Public Releases
#1

Since the last public update m sometimes getting an error saying something like sandbox can’t open console.sh

Since the problem came I am not getting any prints on the sublime text 3 terminal. Only the Mac Terminal is working at the moment.

Any ideas?

#2

Can you copy/paste the exact error message?

Rob

#3

I would, but for some reason the error message is not coming anymore! Unfortunately the sublime terminal is still not working.

Here you can see how the actual terminal is working but not the one at the sublime editor!

2ppmvj8.jpg

#4

I am getting the same, but every time I run the simulator, image attached… Running El Capitain 10.11 and corona sim Version 2015.2731 (2015.10.5)

I am using Outlaw- No messages except

Outlaw

Approximate lines of source code: 22680
Project sandbox: /Users/aleccockleNewMacbook/Library/Application\ Support/Outlaw/Sandbox/441

Mac Terminal runs -as before but only

Last login: Fri Oct 16 19:45:36 on ttys001
Alecs-MacBook-Retina:~ aleccockleNewMacbook$

No Prints being output to either
 

#5

Amazing… I have had this problem since the last three days. Now I have just run again after a system restart and all is running ok!!!

Reminds me of the joke. three engineers in a car and it wont start. Motor engineer, tried everything, Electrical engineer tried.

Software engineer said " all get out, Close the door. Get back in and press start! …

#6

Ok, It is re-occurring!

BYPASS:

Before each test simulator run ensure the MAC terminal is closed down. If not the error occurrs as described. In earlier versions the terminal would create a new window. This was also a pain as you could finish with a large array of test windows.

If a fix is attempted here then a choice of keep or destroy old terminal windows might be useful…

#7

I’ve asked Engineering about this.

Rob

#8

Thanks Rob

#9

Sounds like Outlaw should be running the Simulator with  -no-console YES  but you’d have to ask the Outlaw folks about that.

#10

Thanks-will be in touch.

#11

You can add that line in the Advanced area of Preferences in Outlaw. See the picture below – and I’ll look at adding that internally in the next update.

 Jay

OutlawPreferencesNoConsole.jpg

#12

Thank Jay,  This solve the problem.

#13

Any idea on how to fix this on sublime text 3

#14

I dont use sublime for corona but looking in the sublime help and combining the input from above I would suspect the help page

http://sublimetext.info/docs/en/reference/build_systems.html might be a pointer.

see section shell…

e.g.

shell Optional. If true, cmd will be run through the shell (cmd.exe, [](http://sublimetext.info/docs/en/reference/build_systems.html#id1)bash…).   Try modification to include  e.g. cmd.exe, “-no-console YES” . No idea if this will work but might be clue…

#15

Have the same error on sublime text 3 too.
Can’t find a solution for that :frowning:

#16

Aah I just solved the issue for sublime text 3.
I disabled the autostart of the terminal when corona ist starting by running this command in the terminal window:
defaults write com.coronalabs.Corona_Simulator no-console -bool yes

Now I get prints and all that in the sublime text console again.

#17

Great Well sorted… Useful tip

#18

It would be better to add the -no-console YES arguments to the invocation of Corona Simulator in your Sublime config.  What you’ve done is turn off the Corona Console globally so it will no longer appear even if you run the Simulator by itself.

If you’re using Sublime Text you should check out Corona Editor which integrates the Corona Simulator with Sublime.

#19

Can you copy/paste the exact error message?

Rob

#20

I would, but for some reason the error message is not coming anymore! Unfortunately the sublime terminal is still not working.

Here you can see how the actual terminal is working but not the one at the sublime editor!

2ppmvj8.jpg