Is there a way to view crash reports created on the device?

[ChrisR]

I have an occasional crash in my app while running on my iPad that I can't recreate in the simulator.  Is there a way to view those crashes/error logs that happen on the device?

Thanks

[Conrad Irwin]

Hi Chris,

You can use the Organizer window from XCode. Just boot XCode and then
when it asks you what you'd like to open, jump to the "Window" menu
and then click Organizer. One of the sub-windows inside Organizer is
"Devices"; which contains both the crash logs and the console for any
connected device.

Hope that helps,

Conrad

[Andy Waite]

I guess it won't be possible to symbolicate RubyMotion iOS crash logs though? (i.e. determine which line corresponds to the crash).

Andy

[Laurent Sansonetti]

It's possible to do it by hand, by using the atos(2) command line tool and the .dSYM bundle that is generated by the build system. The load address parameter to atos (-l) can be retrieved from the crash report, it's the first address below "Binary Images".

I plan to work on a rake task that automatizes the whole process (retrieve the crash logs from the device and symbolicate their content).

Laurent

[Francis Chong]

can you provide more details on how to do it by hand?

[Francis Chong]

I'm using Crittercism to collect crash reports for iOS apps. Using Crittercism in RubyMotion is same as that in XCode. 

The only problem I got is the stack trace i found on Crittercism cannot symbolicate with their automatic process. I suspect I would have to symbolicate them myself or wait them support RubyMotion.

Talking about symbolicate myself, Cannot found document on this topic yet. I was trying to use method described in (http://stackoverflow.com/questions/1460892/symbolicating-iphone-app-crash-reports), cannot yet get them working on RubyMotion. So I'm pretty much stuck with hundreds of crash logs look like this: http://cl.ly/image/2k3a1H1b3P1R :(

[Laurent Sansonetti]

You can use the following command:

$ atos -l <load-address> <call-stack-addresses...>

load-address is the first address below "Binary Images". 

call-stack-addresses are the list of addresses that you see in the exception message (in your case, 0x5217b7 0x528b41 ...).

You need to be in the same directory as the .dSYM bundle too. It can be a bit tricky, but I'm working on automatizing this :)

Laurent

[Francis Chong]

Thanks. I'm using Crittercism now and it seems it symbolize the log quite well:

http://cl.ly/image/371E2i020w36

[Daniel R]

Has there been any progress on this, Laurent?

I wrote up what I've been doing to understand crash logs I get via email: http://danramteke.com/devlog/2013-12-04/atos.html