3 ms·
You probably know this, but relying on your local machine and storage for this is a bad idea for production apps. There are a ton of services that handle all t
by alex_suzuki 4y ago
You probably know this, but relying on your local machine and storage for this is a bad idea for production apps.
There are a ton of services that handle all the “mechanical” stuff for you (e.g. AppCenter, ex-HockeyApp), and you can just look at symbolicated crash in your browser.
- saagarjha 4y agoFor production apps I would centralize symbols, yes. But I have a strong disdain for crash reporting services, which are typically authored by people who are designing for aggregating crashes and showing pretty charts rather than really getting deep into the actual log itself. Most have pitifully less information than an actual crash log would–often missing thread state, exception codes, and memory mappings.