Pro Tip iPad Windows Special Edition™ (Part II)

And, unfortunately, the view's traitCollection is not updated on iOS/iPadOS 18.

So now you're going to have two code paths for tracking your app's overall state.

Fun.

But we got what we wanted: Windows!

Pro Tip iPad Windows Special Edition™ (Part III)

This is going to catch a lot of folks off guard. Things like widgets not updating because you update a shared container when the app goes into the background are going to be super hard to track down.

If you look at the behavior of Stage Manager on iPadOS 18, it was trying to insulate apps from this behavior with the "task collections": you got delegate callbacks when those changed.

That no longer happens. Beware.

Pro Tip iPad Windows Special Edition™ (Part IV)

The "am I active or not?" question is not easy to answer in a way that works well on both iPhone and iPad.

The reason is that the iPad, with windows, reports activeAppearance predictably as windows become frontmost or not.

The iPhone, however, reports .inactive, then .active as you put the app in the background. When you return to the foreground, .active, then .inactive, then .active is reported.

So you save state returning to foreground…

Dupe this:

FB18443571: It's impossible to know when to save view state across platforms.

• SceneDelegate doesn't report activation/deactivation of windows on iPad.
• UITraitCollection activeAppearance changes are erratic on iPhone.

This is a huge problem: every app needs to save view state, sync changes, and perform other background operations when a user switches to another app or the home screen. There isn't a reliable way to know that this has happened in iOS 26.