OSX Simulator crashing after 2830 upgrade

Solar2D General Questions/Discussion
#1

I upgraded to Corona 2830 today to get Google Analytics working and it constantly crashes when the sim is running on my Mac (El Capitan 10.11.3).

I do a build (from Corona Editor 1.6.1) and the simulator comes up running my app, but nothing comes into the simulator console - just blank. I click around in my app for a little while then it just hangs - nothing in the console still, and the OSX spinning colour wheel of death comes up.

Only way to move forward is to force quit the simulator.

Anyone else having this problem? Was working fine in 2806.

#2

Just did a bit more investigation and it seems like it’s related to the new console - tried 2820 and it’s still broken - went back to 2810 and it works.

#3

Checking

#4

If you’re starting the app from Corona Editor you shouldn’t be seeing the Corona Console at all, the app’s output should appear in the Corona Editor console pane (this has always been the case and has nothing to do with the new console).

When you say “I do a build (from Corona Editor 1.6.1)” what precisely are you doing?  In terms of menu items or shortcut keys.

#5

I’m using Run Project from Corona Editor (mapped to command-B).

I like the simulator console better - and previously you suggested I include a user setting of…

{

“corona_sdk_simulator_show_console”: true,

}

and my key bindings…

[

    { “keys”: [“super+b”], “command”: “run_project” },

]

#6

So running the project rather than building … well, that should work (but you’re customizing things so it’s not tested).  I’ll take a look.

#7

Customised? Those were settings you sent me on another ticket. Do you think it’s the simulator console call that’s causing it? Not sure the key mapping could be doing it?

#8

Customized in the sense you are off the beaten (tested) track because you are using advanced options.

It’s definitely an interaction between Sublime Text and the new Corona Console caused by setting  “corona_sdk_simulator_show_console”: true  … the keymapping doesn’t appear to matter.

I’m looking at what can be done to make  “corona_sdk_simulator_show_console”  work but your quickest resolution will be to set that to false (or remove it from your Corona Editor preferences).

#9

Upgraded to 2866 and this issue went away - thanks Perry.

#10

Just did a bit more investigation and it seems like it’s related to the new console - tried 2820 and it’s still broken - went back to 2810 and it works.

#11

Checking

#12

If you’re starting the app from Corona Editor you shouldn’t be seeing the Corona Console at all, the app’s output should appear in the Corona Editor console pane (this has always been the case and has nothing to do with the new console).

When you say “I do a build (from Corona Editor 1.6.1)” what precisely are you doing?  In terms of menu items or shortcut keys.

#13

I’m using Run Project from Corona Editor (mapped to command-B).

I like the simulator console better - and previously you suggested I include a user setting of…

{

“corona_sdk_simulator_show_console”: true,

}

and my key bindings…

[

    { “keys”: [“super+b”], “command”: “run_project” },

]

#14

So running the project rather than building … well, that should work (but you’re customizing things so it’s not tested).  I’ll take a look.

#15

Customised? Those were settings you sent me on another ticket. Do you think it’s the simulator console call that’s causing it? Not sure the key mapping could be doing it?

#16

Customized in the sense you are off the beaten (tested) track because you are using advanced options.

It’s definitely an interaction between Sublime Text and the new Corona Console caused by setting  “corona_sdk_simulator_show_console”: true  … the keymapping doesn’t appear to matter.

I’m looking at what can be done to make  “corona_sdk_simulator_show_console”  work but your quickest resolution will be to set that to false (or remove it from your Corona Editor preferences).

#17

Upgraded to 2866 and this issue went away - thanks Perry.