Several years ago, we started stripping native symbols from Debug builds by default because it would shrink the app size, which would make transferring/installing the app faster on device.
Unfortunately this makes crash reports quite useless. Symbolicating crash reports is sometimes possible, but:
It that would require us to teach developers how to do it, and it's not entirely trivial.
It only works on offline symbolication, once you have a crash report (which a lot of people struggle to even find) - in particular it wouldn't work for the native stack trace that is printed by the app and shows up in the IDE's Application Output.
Because of 1. it adds a "file issue or google, get feedback about how to symbolicate, reproduce issue again" loop to developer's lives - which might be avoided in the first place if we just printed a better stack trace in the Application Output's pad in the IDE.
rolfbjarne
commented
5 months ago
Several years ago, we started stripping native symbols from Debug builds by default because it would shrink the app size, which would make transferring/installing the app faster on device.
Unfortunately this makes crash reports quite useless. Symbolicating crash reports is sometimes possible, but:
Case data:
NoSymbolStripis mentioned (2 open, 41 closed): https://github.com/xamarin/xamarin-macios/issues?q=is%3Aissue+sort%3Aupdated-desc+nosymbolstrip+ - most of these is me asking the reporter to disable stripping and then trying again.So the suggestion would be to disable stripping symbols by default in Debug builds.