UIApplication.State inactive clarification

Hi,

The documentation for UIApplication.State's inactive state says:

"The app is running in the foreground but is not receiving events."


Could anybody expand on exactly what events are not received? (And/or maybe what this means in terms of changes to runloop event/source configuration, if that helps give a more precise explanation of any limitations?)


Is it only touch events that are ignored, or are there other things that won't work? (Timers on the main run loop still and UI activity triggered by them still seem to work from my observations.)


Thanks,

Rob

Up vote post of software_dev_user Down vote post of software_dev_user
1.2k views
Posted by
software_dev_user
Reply
Add a Comment

Accepted Reply

This state typically shows up when the system has brought up some UI in front of the app, such as the Wi-Fi selection dialog. The events in question are UI events; the app is still in the foreground and thus timers and so on are still running.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware 

let myEmail = "eskimo" + "1" + "@apple.com"
Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Post marked as solved
Add a Comment

Replies

This state typically shows up when the system has brought up some UI in front of the app, such as the Wi-Fi selection dialog. The events in question are UI events; the app is still in the foreground and thus timers and so on are still running.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware 

let myEmail = "eskimo" + "1" + "@apple.com"
Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Post marked as solved
Add a Comment

Thanks very much Quinn. (Just for other readers, which is in line with Quinn's answer, we also see this when a Touch ID prompt is being displayed.)

Posted by
software_dev_user
Up vote reply of software_dev_user Down vote reply of software_dev_user
Add a Comment