“offloading”

I've observed the same behaviour with one of our Apps - if the App is offloaded, the device will continue to recieve push notifications. Since the App is (effectively) uninstalled, it seems that there's not delegate to call-back to, and touching the notification banner does nothing, doesn't even show a message that the app has been offloaded that you would see when you touch the App icon. This behaviour persisted for me for a couple of days, although I haven't tested longer than that to know if it the APNs token remains valid indefinitely. I likewise was unable to find any definitive developer documentation about how offloaded apps effect push notifications (or technical documentation on offloaded apps in general). Were you able to find any information Sumanth?

Hi again,Thanks for the reply. This makes me aware of a number of risks we did not appreciate.Could I just follow up to be sure I understand them right? Specifically, even after we‘ve switched to CA-signed server certificates, you point out two major reasons we should still avoid performing our own server trust challenge evaluation (or indeed handling any authentication challenge) with background sessions:The first reason is we might be penalized by the iOS resume rate limiter:For background sessions specifically, the resumes necessary to handle this authentication challenge counter against the resume rate limiter.Note This applies to all authentication challenges, not just server trust challenges.My question is, is this an issue even if I'm doing something computationally cheap like checking the certificate's common name? In other words, do you mean that any URLSessionDelegate object which implements urlSession(_ session: didReceive: completionHandler:) is a handicap for background execution, because simply

Same here. What worked for me was deleting the ‘prepared’ install bits, from the iPhone Storage settings after the install failed a couple of times, then re-downloading. The subsequent attempt to download completed, “prepared”, and “verified”, and successfully updated the phone (iPhone 7). [For the curious, I have a 128GB iPhone 7, which has about 60GB free. Ample space for the OS to download the update bits, expand them, and do what it needed to do to effect an install without offloading apps or other data to introduce confounding variables to the process.]

You're right Scott. Offload unused apps somehow was enabled. It did an awful job of determining inactivity. For example it removed 1Password which I use seveeral times a day. It also blew apart most folders and couldn't bring apps back as advertised.Thanks,Tom

Have you checked to see if your Offload Unused Apps is enabled? Is it possible that these are apps that you have not used in a while and the new OS has removed them from your device due to inactivity in order to free up space on your phone?

From what I have been reading, APFS changes how Fusion works. It's now just a cache repository for meta data, readback cache and writeback cache. It will assist in directory listing. App Nap, Prelinking and directory lookups would likely be the most impacted.I do not know if it will offload files to the SSD that are frequently used like in days past. I'm not saying this is fact but supposition based on what little information I've found so far. The nature of APFS means it is always optimizing content in order to reduce fragmentation so logically it makes sense that it would work off of the HDD and use the Fusion as a cache - such as that for app nap. Anyone else have insight on APFS and Fusion topology? Has it changed Fusion fundamentally?