So I added multiple window support for iPad in an app.
Now I understand if there are 'windows' open killing the window in the app switcher won't cause the app to terminate.
When I have two windows open in the same "scene" in split view...and I kill that scene in the app switcher, Xcode immediately terminates my debug session as if the app has been killed.
However, when I hit run to try to get a "fresh" run of the app, my split view windows are restored (I'm not using a state restoration activity)..and application:didFinishLaunchingWithOptions: is *not* called.
So even though all windows are closed (users sometimes kill apps by removing them in the app switcher manually) my app is skipping the -application:didFinishLaunchingWithOptions method in the app lifecycle.
Are users no longer able to really "quit" apps in the App Switcher when an iPad app supports multiple windows? How can a user terminate an app?
Now I understand if there are 'windows' open killing the window in the app switcher won't cause the app to terminate.
When I have two windows open in the same "scene" in split view...and I kill that scene in the app switcher, Xcode immediately terminates my debug session as if the app has been killed.
However, when I hit run to try to get a "fresh" run of the app, my split view windows are restored (I'm not using a state restoration activity)..and application:didFinishLaunchingWithOptions: is *not* called.
So even though all windows are closed (users sometimes kill apps by removing them in the app switcher manually) my app is skipping the -application:didFinishLaunchingWithOptions method in the app lifecycle.
Are users no longer able to really "quit" apps in the App Switcher when an iPad app supports multiple windows? How can a user terminate an app?