unhandledError event

Other
#1

I catch the unhandledError message and store the results in a database, but I am finding that the key information, file name and line number are missing from the info.  Am I missing something?  I am saving event.errorMessage and event.stackTrace.  

This is the info I am getting:

errorMessage:

‘?:0: attempt to index field ‘‘view’’ (a nil value)’

stackTrace:

stack traceback:

    [C]: ?

    ?: in function ‘?’

    ?: in function ‘?’

    ?: in function ‘?’

    ?: in function <?:3157>

    ?: in function <?:218>

I’ve got some line numbers, but have no idea what file they are in.  I can’t get the bug to reproduce in the simulator which provides me with more info then the unhandled error and I’m at a loss as to where to look for the bug.

#2

Are you doing this with your app on device or in the simulator?

#3

On device,  I can’t reproduce in the simulator.   When I do have errors I can reproduce I will get something like the above sent to my database, and when I run it in the simulator the file name and line number show up.  

I suppose I could turn off the error catching and see if it displays more information in the android logcat console. Currently I’m using the unhandlederror to catch them, and then doing a print to the console.  

#4

Errors on device but not on the simulator 90+% of the time is a file name problem.  The Simulator is not case sensitive, the device is.  This includes all audio and image files as well as module names (things you require).  I would turn off the error trapping and use prints and the console log to try and diagnose it.

#5

Are you doing this with your app on device or in the simulator?

#6

On device,  I can’t reproduce in the simulator.   When I do have errors I can reproduce I will get something like the above sent to my database, and when I run it in the simulator the file name and line number show up.  

I suppose I could turn off the error catching and see if it displays more information in the android logcat console. Currently I’m using the unhandlederror to catch them, and then doing a print to the console.  

#7

Errors on device but not on the simulator 90+% of the time is a file name problem.  The Simulator is not case sensitive, the device is.  This includes all audio and image files as well as module names (things you require).  I would turn off the error trapping and use prints and the console log to try and diagnose it.