How come Crash Reports Don't Include the NSException name and reason when a crash is caused by a raised exception?

When running into a hard to reproduce crash that only occurs in a production build it would be helpful to get more detailed information about the thrown exception. As far as I can tell, Crash reports don't include the NSException's name, reason, or userInfo. Is there any reason why this isn't included in Crash reports provided to developers?

Someone else asking something similar here: https://stackoverflow.com/questions/73327915/how-do-you-add-diagnostic-information-to-ios-crash-reports

Is there any reason why this isn't included in Crash reports provided to developers?

Yes.

(-:

I presume you meant “What is the reason … ?” That’s not a question I can answer because I generally don’t discuss Apple’s internal processes here. However, my experience is that the absence of useful info in a crash report is usually explained by one of three things:

  • Privacy concerns

  • Bugs

  • No one thought it’d be useful

The best way to tease these apart is to file an enhancement request for the crash report to include that info.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

How come Crash Reports Don't Include the NSException name and reason when a crash is caused by a raised exception?
 
 
Q