errors in Corona Terminal

Solar2D General Questions/Discussion
#1

Hi all,

I’ve been using Corona for more than a year. Till last stable release when I had some errors in code (like calling variable that wasn’t declared earlier ) I had error shown in Corona Terminal (error in file on line nil value etc).

Now (Version 2012.894 (2012.8.27)) I know that I have an error, because app doesn’t behave in simulator like I expected. Corona Terminal doesn’t show anything. But sometimes it shows error in Corona Terminal. I don’t know the pattern, which errors are good for terminal.

When I launch app in debugger I see the error description in Terminal, app in simulator stops.

But using debugger only for showing errors isn’s effective. After the error I have to relaunch debugger. Simple Cmd + R after change in code doesn’t affect terminal.

Any idea?

Thanks

Marcin. [import]uid: 67745 topic_id: 32552 reply_id: 332552[/import]

#2

Sorry to bring an old topic but this is happening to me with the new public and daily builds of Corona.

Last year’s version showed me the errors, not anymore. And I’ve made sure that “Show Runtime Errors” is checked in the Preferences.

#3

What version of Corona SDK are you using?

Are you using any IDE like glider or Corona Complete?

#4

Hi Rob, thanks for the fast response,

Using latest build and latest public. Not showing any errors. However I reverted to 2012.971 (last year’s public version) and it shows me errors.

I’m doing something as simple as: 

print ab

Which throws me an error in 2012’s version but not in 2013’s.

And nope, I’m not using any IDE. Plain TextEdit.

#5

printing works for me.  Too well at times.

#6

I created a new user in my Macbook and then created a new project. Errors are showing in there but not in my main user. Where can I delete all the files Corona makes so I can perform a clean install?

#7

I also have this problem. None of the runtime errors are showing in terminal even with box checked in Simulator Preferences.

I’m using the 2013.1100 daily build.

#8

Can you do a simple test project.  Only have one file in the folder.  And only have one line in the file:

print(“Hello World”)

And see if that works.

#9

print works fine, it’s just runtime errors such as syntax errors, etc… that are no longer appearing.

#10

Sorry to bring an old topic but this is happening to me with the new public and daily builds of Corona.

Last year’s version showed me the errors, not anymore. And I’ve made sure that “Show Runtime Errors” is checked in the Preferences.

#11

What version of Corona SDK are you using?

Are you using any IDE like glider or Corona Complete?

#12

Hi Rob, thanks for the fast response,

Using latest build and latest public. Not showing any errors. However I reverted to 2012.971 (last year’s public version) and it shows me errors.

I’m doing something as simple as: 

print ab

Which throws me an error in 2012’s version but not in 2013’s.

And nope, I’m not using any IDE. Plain TextEdit.

#13

printing works for me.  Too well at times.

#14

I created a new user in my Macbook and then created a new project. Errors are showing in there but not in my main user. Where can I delete all the files Corona makes so I can perform a clean install?

#15

exactly, same thing happening here even with the latest build. Could it have something to do with profiles inside OS X?

#16

Can everyone open up the preferences for Corona SDK and make sure the “Show Runtime Errors” is checked.

Also check this blog post and see if any of these conditions are true:

http://www.coronalabs.com/blog/2013/03/13/wednesday-faq-runtime-error-listener/

#17

Show runtime errors is checked in preferences

I get an occasional pop up error, (but not always)

Either way, no errors are shown in the console, only using print displays in console.

#18

I also have this problem. None of the runtime errors are showing in terminal even with box checked in Simulator Preferences.

I’m using the 2013.1100 daily build.

#19

Can you do a simple test project.  Only have one file in the folder.  And only have one line in the file:

print(“Hello World”)

And see if that works.

#20

print works fine, it’s just runtime errors such as syntax errors, etc… that are no longer appearing.