Well, In my original post, there wasn't a "crash" but just a straight out applicationWillTerminate not getting called at all without notice. This method being called (when expected) is really kind of important for applications that may have uncommitted resources hanging out in the breeze.The verbiage "Application can be killed immediately when user is shutting down or logging out" seems to indicate when the user is shutting down or logging out of the machine/account; Not just normally quitting an application.Bug will be filed in the next day or two.- Neil

Yep, that did the trick, thanks for that. BUT "Application can be killed immediately when user is shutting down or logging out" does not apply in my case. All I am doing is quiting the app, NOT "shutting down or logging out"; This is obviously a huge bug and should not be the default for macOS.Regards,Neil

Thanks PBK, As per my post; this is a macOS application (not iOS). Yes, the default generated App terminates and UIKit is not a factor. Unfortunately, applicationWillTerminate never gets called so we can correctly clean up server connections and whatnot.Again, I created a brand new "out of the box" application to confirm. In both Objective-C (and Swift); applicationWillTerminate is not called. NSLog and Breakpoints applied. applicationDidFinishLaunching gets executed.Regards,Neil