I'm working on an iOS app. I need to keep refreshing some data even when the app is in the background. Unfortunately, the older (and simpler) method to have tasks running in the background are deprecated.
So I've been looking at what is the new standard, which seems to be stuff from the BGBackgroundTask framework. I've also been looking at URLSession configured for background because that's what I use in a previous project. In that other project, I've been using a dataTask because I'm not really downloading files, just data from a web server.
The background-based URLSession seems easier to setup than all the paraphernalia required to get the background tasks to work.
However, I've been a bit worried when I read this bit from the doc: For long-running and nonurgent transfers, you can create tasks that run in the background. These tasks continue to run even when your app is suspended, allowing your app to access the downloaded file when the app is resumed.
That seems good but, what if after downloading, I need to schedule another download? So, it seems to me that I would still need to use the BGBackgroundTask framework to kick a download.
Am I right in my assumption?
Thanks in advance for any pointer or info!