Yup, we've been back and forth on this most of the day. If you can test with objectiveC then please do, whenever you have the time of course, I plan on doing the same. Running in the background and suspend/resume, to me, are two different things. I'm not sure how "running in the background" or a multitasking springboard (that you could get with jailbreaking) really came into this, just looking for confirmation that suspend/resume is not supported on the hardware, because IOS 4.x definitely supports it, and the apps I run on that basic device seem to all respond appropriately. The documentation I've found says that apps bulit against SDK4+ should receive a "resign activation" notification instead of simply receiving a WillTerminate() notification, yet MT applications only ever see a WillTerminate - that same documentation states that apps built against SDK3+ receive a WillTerminate() immediately after a DidEnterBackground(), which is exactly the behavior I am seeing - at least on a touch 2nd gen, with 4.2.1. I think it is worth investigating, to be honest. Either I need to manually save state and re-enter the app at a specific UIViewController with a specific state, or it should happen automatically - which, for IOS 4.2.1 all documentation says it should be. If there is a device limitation, I can understand, but then again - the behavior of the apps that are on the device says differently.
-- View this message in context: http://monotouch.2284126.n4.nabble.com/Terminating-on-suspend-IOS-4-2-target-behavior-tp4656259p4656331.html Sent from the MonoTouch mailing list archive at Nabble.com. _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
