Newbie Help - Failing on Device

Getting Started Newbie Questions
#1

Hi,
I am kinda new at this so sorry if this question is vague. I have kind of written an app (beginning stages) and it works perfectly on Corona and in xCode (havent set up iOS yet). When I installed it on my S2 I get the following error - “Runtime Error ?:0: attempt to index a nil value”… I don’t expect anyone to be able to tell me what the error is - what I want to know is how do I go about debugging my code to find this error… At the moment I am at a complete loss… How do I see the log files?

Thanks

Craig [import]uid: 184705 topic_id: 36249 reply_id: 336249[/import]

#2

Kind of figured it out… It appears that the new tab bar widget is having an issue, my code was directly copied from the sample widget (build 1035) and was only there as a place holder till I needed it - I have commented it out so I can still move on. The sample widget works (although it looks bad) so I am not sure why mine doesn’t - literally a copy and paste (including images).

I would still appreciate some help with debugging builds as I can almost guarantee that I will get more issues. [import]uid: 184705 topic_id: 36249 reply_id: 144000[/import]

#3

For Android, there is a set of tools called “Android Debug Bridge” or adb. These get installed as part of installing the Google Android SDK developer package. Once you have that installed, you can use the command line command:

adb logcat

to dump the log of the device as long as it’s tethered to the USB port.

[import]uid: 199310 topic_id: 36249 reply_id: 144069[/import]

#4

Thanks Rob - Took some time but I can view the logcat now… Lets hope I don’t need to use it too often… [import]uid: 184705 topic_id: 36249 reply_id: 144163[/import]

#5

Kind of figured it out… It appears that the new tab bar widget is having an issue, my code was directly copied from the sample widget (build 1035) and was only there as a place holder till I needed it - I have commented it out so I can still move on. The sample widget works (although it looks bad) so I am not sure why mine doesn’t - literally a copy and paste (including images).

I would still appreciate some help with debugging builds as I can almost guarantee that I will get more issues. [import]uid: 184705 topic_id: 36249 reply_id: 144000[/import]

#6

For Android, there is a set of tools called “Android Debug Bridge” or adb. These get installed as part of installing the Google Android SDK developer package. Once you have that installed, you can use the command line command:

adb logcat

to dump the log of the device as long as it’s tethered to the USB port.

[import]uid: 199310 topic_id: 36249 reply_id: 144069[/import]

#7

Thanks Rob - Took some time but I can view the logcat now… Lets hope I don’t need to use it too often… [import]uid: 184705 topic_id: 36249 reply_id: 144163[/import]

#8

Kind of figured it out… It appears that the new tab bar widget is having an issue, my code was directly copied from the sample widget (build 1035) and was only there as a place holder till I needed it - I have commented it out so I can still move on. The sample widget works (although it looks bad) so I am not sure why mine doesn’t - literally a copy and paste (including images).

I would still appreciate some help with debugging builds as I can almost guarantee that I will get more issues. [import]uid: 184705 topic_id: 36249 reply_id: 144000[/import]

#9

For Android, there is a set of tools called “Android Debug Bridge” or adb. These get installed as part of installing the Google Android SDK developer package. Once you have that installed, you can use the command line command:

adb logcat

to dump the log of the device as long as it’s tethered to the USB port.

[import]uid: 199310 topic_id: 36249 reply_id: 144069[/import]

#10

Thanks Rob - Took some time but I can view the logcat now… Lets hope I don’t need to use it too often… [import]uid: 184705 topic_id: 36249 reply_id: 144163[/import]

#11

Kind of figured it out… It appears that the new tab bar widget is having an issue, my code was directly copied from the sample widget (build 1035) and was only there as a place holder till I needed it - I have commented it out so I can still move on. The sample widget works (although it looks bad) so I am not sure why mine doesn’t - literally a copy and paste (including images).

I would still appreciate some help with debugging builds as I can almost guarantee that I will get more issues. [import]uid: 184705 topic_id: 36249 reply_id: 144000[/import]

#12

For Android, there is a set of tools called “Android Debug Bridge” or adb. These get installed as part of installing the Google Android SDK developer package. Once you have that installed, you can use the command line command:

adb logcat

to dump the log of the device as long as it’s tethered to the USB port.

[import]uid: 199310 topic_id: 36249 reply_id: 144069[/import]

#13

Thanks Rob - Took some time but I can view the logcat now… Lets hope I don’t need to use it too often… [import]uid: 184705 topic_id: 36249 reply_id: 144163[/import]