Thanks, Matt for your reply.
If you are running a background URLSessionDataTask then this is also not intended to work either. Only URLSessionUploadTask and URLSessionDownloadTask should be used in a background URLSession.
Yes, I'm using the URLSessionDataTask but it's a default configuration, what I thought that It can be work the same way like we generally did for a silent push notification (Invoke app in the background). I also tried to add backgroundhandler block which generally waits for some time before going to suspend state.
If you need to upload the status of a network call, then you would need to save this status for either your foreground session when your app is no longer suspended and active, or you could investigate whether a URLSessionDataTask works with a BGAppRefreshTaskRequest. The pitfall with the BGTask side of things is that these tasks are not intended to run frequently and you should expect that there could be long gaps in-between running these tasks.
I thought earlier to wait for the foreground state and update the status but the API token might expire during that time.
I can check for BGAppRefreshTaskRequest.
Topic:
App & System Services
SubTopic:
Networking
Tags: