Post

Replies

Boosts

Views

Activity

Comment on BGProcessingTask expirationHandler — No way to distinguish expiration reason
Our app needs to perform background video compression and upload, and this work can take around 30 minutes to 1 hour. The problem is that expirationHandler is called irregularly. Sometimes it seems related to task duration, and sometimes it seems related to system resources, but after many tests we still could not find a clear pattern.
7h
Comment on BGProcessingTask expirationHandler — No way to distinguish expiration reason
Our app needs to perform background video compression and upload, and this work can take around 30 minutes to 1 hour. The problem is that expirationHandler is called irregularly. Sometimes it seems related to task duration, and sometimes it seems related to system resources, but after many tests we still could not find a clear pattern.
7h
Comment on BGProcessingTask expirationHandler — No way to distinguish expiration reason
Our app needs to perform background video compression and upload, and this work can take around 30 minutes to 1 hour. The problem is that expirationHandler is called irregularly. Sometimes it seems related to task duration, and sometimes it seems related to system resources, but after many tests we still could not find a clear pattern.
7h
Comment on BGProcessingTask expirationHandler — No way to distinguish expiration reason
Our app needs to perform background video compression and upload, and this work can take around 30 minutes to 1 hour. The problem is that expirationHandler is called irregularly. Sometimes it seems related to task duration, and sometimes it seems related to system resources, but after many tests we still could not find a clear pattern.
7h