@Polyphonic thank you for answering. Our issue is related to the download procedure and not the expiration of the asset after download completes.
For example here is a use case: a user adds 3 assets to download, one is currently downloading and the other 2 are in queue, then the device goes offline and after 12 hours connects to the internet again. The first asset will continue to download and will be playable, but the url of the second asset has expired (due to url signing) We tried to use the HTTP cache policy to overcome this, but with no success. Is there anything else that you suggest?
gcharita
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution