Dear Kevin, thanks a lot for getting back so quickly & your detailed response! The problem I'm trying to solve is to reliable sync data from a BLE peripheral in Background over a longer period of time — either during the day or the night — between our user opening the App. However, once the app is killed, the task is no longer scheduled in the Background until the App is reopened, the Task resubmitted & re-scheduled. So I'm looking for a way to rerun the Task even though the App was killed. Is there any way to launch the App into Background "later" as you mentioned other than having to open the App again?

Thanks such much again for your time & effort Kevin! I did look into the Documentation & tried different approaches but none seems to work. I also found a BLE sample project on the Apple Developer Documentation & it is also terminated after some time. However, unlike the Documentation states, I wasn't able to implement State Restoration and receive Characteristic updates once the App is terminated because of Memory Pressure. But I will continue to investigate into this direction. May I suggest to update the Documentation around Background Tasks to reflect the iOS Background Execution Limits https://developer.apple.com/forums/thread/685525 Neither the WWDC session nor the Documentation mention these limits. Additionally, several WWDC session like "Background execution demystified" & "Why is my app getting killed" are no longer available. Thanks a lot again

I just submitted FB21360292 — I didn't know this was possible for Documentation too! Thanks a again for your great support & all the best!

Thanks a lot for your quick reply. I made sure that the requirements you mentioned are met & which left me with the following scenario: Peripheral is connected in the Foreground App moves in the Background At some point the App is terminated because of using too much memory Peripheral moves out of range & disconnects App is launched in the Background and willRestoreState is called correctly App is again suspended and terminated at some point Peripheral moves into range and should re-connect by launching the App in the Background again Up until 7. everything works as expected. So I assume there needs some work to be done in willRestoreState() to make sure the Peripheral can connect again. Unfortunately, the documentation is very sparse at this point. Thanks a lot for your help again! Highly appriciated

I was able to resolve the issue! Thanks a lot for your support