PPS Shoutout to Uli Kusterer - my code was originally based on his UKCrashReporter. PS The crash catcher that appeared in earlier versions of NetNewsWire itself had a crashing bug (briefly): it would crash if there were no crash logs found! Which was self-healing - because once there was a crash log it wouldn’t crash any more. This crash reporter is just for the non-MAS build. For that build, for better or worse, I’ll rely on Apple collecting and reporting crash logs. Important note: this code will not be part of the Mac App Store build. I’m rewriting it in Swift, but using the same logic. I think this is the first time that I’ve looked back to old NetNewsWire code. (And here’s the code from NetNewsWire Lite 4.) The code isn’t complete yet, but here’s the start. It’s a few dozen lines of code compared to adding an entire framework. And it means one less dependency, and it means code I fully understand and control. This isn’t as slick as an in-process crash catcher - but this system worked for me for years. (A window appears with the text of the crash log, a place to add more info, and some buttons - send or don’t-send.) The way it works: at launch time it looks for a crash log in the appropriate folder, and if the most recent crash log has not been seen before, then it prompts the user to send it it in. This means I could use the crash log catcher I used to use in NetNewsWire 3 and NetNewsWire Lite 4. I thought some more about it, and did some research, and I learned that crash logs are still written to disk. So I forked PLCrashReporter with the idea of fixing those errors myself, but then ran into territory I’m not familiar with and not confident about, so I stopped and deleted my fork. See postscript.)īut when I tried to build it there were a bunch of deprecation warnings (OSSpinLock, for instance) - and, since I treat all warnings as errors, it wouldn’t build.
#Netnewswire 3.3.2 update#
(Correct me if I’m wrong about this! Update next day: I am wrong. So I went to add it to NetNewsWire, and here’s what happened:īecause of Apple’s new app notarization service, I needed to have PLCrashReporter get built along with the rest of the app - this way I could turn on the required “hardened runtime” setting. The consensus choice for crash reporters is PLCrashReporter.
0 kommentar(er)
