{"id":48305,"date":"2025-07-01T15:05:59","date_gmt":"2025-07-01T19:05:59","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=48305"},"modified":"2025-07-17T14:07:32","modified_gmt":"2025-07-17T18:07:32","slug":"ipados-windows-mess-up-data-saving","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2025\/07\/01\/ipados-windows-mess-up-data-saving\/","title":{"rendered":"iPadOS Windows Mess Up Data Saving"},"content":{"rendered":"

Craig Hockenberry<\/a> (Mastodon<\/a>):<\/p>\n

\n

From the very beginning, iOS has had a notion of an app being in the foreground or background. When you saw an app on screen it was active and when it was gone it was inactive.<\/p>\n

[…]<\/p>\n

It was simple system that let you do what you needed to do, when you needed to do it. Now with windows on iPadOS, that’s gotten a lot harder.<\/p>\n

That’s because apps stay active even when their windows do not.<\/p>\n

If you’re using iPadOS 26 and noticing that the saving\/syncing\/exchange of data is not happening, there’s a stupid trick you need to do to get things working: Tap on the home screen to hide the windows (they slide off to the sides of the display). That makes all the apps on screen inactive and triggers the work that they need to do.<\/p>\n<\/blockquote>\n

It seems like there’s a missing API for apps to know what’s happening.<\/p>\n\n

Previously:<\/p>\n