Got a runtime error that doesn't trigger on the simulator.

Solar2D General Questions/Discussion
#1

Hi,

I got a runtime error that pops up on the iOS device, it is a nil error.

But I cannot get it to pop up on the corona simulator.

Which usually means a capitalisation error on my part. 

Is there a way I can force it to trigger on my computer?

 Also if I override the runtime errors the app still works. But I would like to solve it anyway.

Is there a way to get the runtime error to appear on my computer?

#2

Here’s a forum post detailing the same problem and a possible solution.

http://forums.coronalabs.com/topic/55496-just-a-thought/

#3

Thanks, I checked it. But I am working on OSX and the dev said that it doesn’t work well on OSX yet. Will check when he had time to take a look at it.

#4

You probably can’t force a device error on the simulator.  Sure Ed’s filename detector can help, but you’re likely having some other error since you are aware of the case sensitivity issue.  Your best bet is to use “adb logcat” and see what errors are showing up on the device.  I know it’s not a pleasant thing to do, but it’s the right thing to do.

Rob

#5

Here’s a forum post detailing the same problem and a possible solution.

http://forums.coronalabs.com/topic/55496-just-a-thought/

#6

Thanks, I checked it. But I am working on OSX and the dev said that it doesn’t work well on OSX yet. Will check when he had time to take a look at it.

#7

You probably can’t force a device error on the simulator.  Sure Ed’s filename detector can help, but you’re likely having some other error since you are aware of the case sensitivity issue.  Your best bet is to use “adb logcat” and see what errors are showing up on the device.  I know it’s not a pleasant thing to do, but it’s the right thing to do.

Rob