3 ms·
Apple has had anonymous crash reports for years. Unfortunately, they are close to useless, because you get reports only for a tiny fraction of crashes. I assume
by newaccount74 4y ago
Apple has had anonymous crash reports for years. Unfortunately, they are close to useless, because you get reports only for a tiny fraction of crashes. I assume it's either because nobody opts in to share analytics with 3rd party developers, or because Apple is just incompetent and their tech doesn't work.
In any case, I received only a handful of crash reports from Apple. I thought everything was okay, except that customers occasionally reported an issue, but I never got a crash report from Apple that could explain the situation. Until I built my own reporting solution, which just sends a stack trace to my server in a signal handler. I started receiving dozens of crash reports per week.
So while on the one hand I applaud Apple for trying to do the right thing, as a developer I can only say that the crash reports they share with developers are so few they are close to useless.
- wahnfrieden 4y agoYou’re referring to something older
- newaccount74 4y agoSo what's that new framework? Can I use it to reliably transmit stack traces when the app crashes?
- wahnfrieden 4y agohave a look at https://github.com/ChimeHQ/MeterReporter https://github.com/ChimeHQ/MeterReporter which uses the wwdc20 frameworks
- newaccount74 4y agoThank you for the link, this is interesting. It's nice Apple is apparently building support for custom crash reporting into the OS. From a privacy perspective it sounds like it logs exactly the same info that I currently log with PLCrashReporter, except that it only works on macOS 12.
- wahnfrieden 4y agoAh ok