[Resolved] Can't view crash reports or print statement when running from device?

So I just started testing on my device and my app crashes at certain points but I don’t know why because I can’t view my print statements in the Organizer and I don’t get any crash reports. Plus my app works perfect in the simulator, it only crashes on the device. Does anyone have any suggestions on why I don’t get either of these things? [import]uid: 63320 topic_id: 25403 reply_id: 325403[/import]

@dacriburdan
As received this last week on my RSS Feed mail, a new Ansca FAQ (and very nice one btw IMHO) there is one part that probably will help answer your question above, have a look below please:

Question 1:

I can see my “print” messages in the Corona terminal when running the Corona simulator but I don’t see the messages when I’m running on the Xcode iOS simulator or my device. What am I doing wrong?

Answer:

If you are testing iOS devices and loading the app using Xcode, the Xcode console will display the print messages. If you are using the Xcode iOS Simulator, start Mac’s console app and you will see the messages there. If you are testing Android devices, you should download the Android SDK and use “adb logcat” to view print messages (and other device messages).

Tip: I f you don’t see your messages coming out in a prompt manner, add the following to the top of your main.lua file:
[lua]io.output():setvbuf(‘no’)[/lua]

PS: I do use the Organizer to do all the work (install apps, unisntall, see the console looking for “print()” statements, etc) and so I can tell you that if you do so youll be able to see your "prints" right into the Xcode Organizers Console and they will be shown to you with a tag: |notice> beside your own prints.

Hope that help!
Cheers,
Rodrigo. [import]uid: 89165 topic_id: 25403 reply_id: 102602[/import]

Thanks for the reply Rodrigo. I’ve already done all of the above and nothing seems to work. I’m not sure if the is a Corona bug or something on my part.

EDIT: It must have been an issue with my backup because once I restored to a “fresh” firmware everything worked as expected. Thanks! [import]uid: 63320 topic_id: 25403 reply_id: 102604[/import]

WOW!

Glad to hear that mate. :slight_smile:
Have fun,
Cheers,
Rodrigo. [import]uid: 89165 topic_id: 25403 reply_id: 102611[/import]

Pleased to see this is sorted; so often it does seem to be the setvbuf issue.

Marking as resolved :slight_smile: [import]uid: 52491 topic_id: 25403 reply_id: 102651[/import]