iTunes 8.2 Release = Consumer Crash Log Boom to Developers


When iTunes 8.2 debuted in prerelease form (for developers running the iPhone 3.0 beta firmware), one of the more exciting features from the back-end perspective was crash logs being made available via iTunes Connect.

Well, Hassan from Inside Redbox Mobile reminded us that, with iTunes 8.2 going into general availability -- and into the hands of consumers -- developers now have access to the full range of crash logs from their full base of installed customers. Bug. Fixing. Goldmine. (See the Inside Redbox Mobile crash log report, above.)

From the consumer standpoint, the information looks to be as anonymized as anything else sent from iTunes to Apple -- Genius info, for example -- and in exchange for sharing, users will likely get more stable apps.

Sounds good to us!

[Thanks Hassan!]

Have something to say about this story? Leave a comment! Need help with something else? Ask in our forums!

Rene Ritchie

EiC of iMore, EP of Mobile Nations, Apple analyst, co-host of Debug, Iterate, Vector, Review, and MacBreak Weekly podcasts. Cook, grappler, photon wrangler. Follow him on Twitter and Google+.

More Posts



← Previously

Good to Go: Apple's One Billion Dollar North Carolina Server Farm

Next up →

Rogers Canada Now Offering 15GB/$150 for "Heavy Users"

Reader comments

iTunes 8.2 Release = Consumer Crash Log Boom to Developers


So can any developers weigh in (anonymously if necessary) as to exactly what (if any) sandboxed data can be obtained in a crash report?
If, say, my wallet manager application crashes, what data does the developer get?

@icebike you will only see a stack trace of the method that blew up. The actual data the the method blew up with is not displayed in the crash report. The developers have no say into the contents of the crash report.
So if your wallet manager crashes the developer should be able to pin point which line of code it crashed at, and the type of error that caused the crash. The data that caused the crash will not be visible in the crash report.

Thanks, Hassan. That is reassuring.
I've seen other crash dump facilities that exposed all sorts of memory, even from companies (CoughMicrosoftCough) that insist no identifying data was transmitted.