On Sat, Apr 2, 2011 at 9:53 PM, Quincey Morris <quinceymor...@earthlink.net> wrote: > On Apr 2, 2011, at 18:01, Jeffrey Walton wrote: > >> I planned on saving some state when the applicationWillTerminate was >> invoked. Are things working as expected? Should I abandon my plans to >> save state during termination? > > No, you should save the state, but it's explained here: > > > http://developer.apple.com/library/ios/#documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/CoreApplication/CoreApplication.html > > (search for all occurrences of "applicationWillTerminate", since the > information you need is spread out) that you don't get the notification in > the circumstances you describe. > > I think you'll need to force a low-memory termination to test the code path > through 'applicationWillTerminate:'. I couldn't see an easier way to make it > happen with an iOS 4.0 backgroundable multitasking-aware app. > Thanks Quincey. I do see where iOS will terminate the application (SIGKILL) rather than calling applicationWillTerminate (the two paragraphs under "Responding to Application Termination" coupled with foreground/background/suspend state).
It sure would be nice if we could count on applicationWillTerminate all the time. A SIGKILL without applicationWillTerminate seems kind of rude :( Jeff _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
