To my knowledge there is no debugger or terminal output tool for Corona apps running on actual devices. If we can’t have a real-time debugger I would settle for a Terminal console output that would display run-time errors and print statements. Maybe this will come in a future version of the SDK.
Here is what I do to debug on an actual device.
If you have an app that only runs on a actual device I would first load it into the Simulator (“Corona Terminal”) and it will show if you have any major problems with the syntax of your main.lua code and other modules you may be using.
Next I add Alert boxes (for iPhone/iPad) in place of print/debug statements. If you have any screen space available, you could display some short status message/variables on the screen you’re debugging.
I was also thinking about creating a generic “information page” that I could transition in/out of my main display to keep track of variables and program trace/status information. My goal would be to create this once and reuse it among the programs I’m building.
If you have some device specific features that won’t run in the simulator, you could stub out those functions (or simulate the functions) in order to test and debug the rest of the program on the simulator.
I would love to hear how other developers are debugging their programs on actual devices.
Tom [import]uid: 6119 topic_id: 1058 reply_id: 2920[/import]