If you use [imageManager requestAVAssetForVideo…], it’ll return an AVAsset. That AVAsset is actually an AVURLAsset, so if you cast it, you can access it’s –url property. I’m not sure if you can create a new asset out of this, but it does give you the location.
Based on the comments, I’m not entirely sure what the issue is but I hope this code could provide some assistance. Using .album rather than .smartAlbum could also be part of the issue. private var fetchResult: PHFetchResult<PHAsset>! func fetchOptions(_ predicate: NSPredicate?) -> PHFetchOptions { let options = PHFetchOptions() options.sortDescriptors = [ NSSortDescriptor(key: “creationDate”, ascending: false) … Read more
I just went through this too. By my tests the issue appears on devices that have the “Optimize Storage” option enabled and resides in the difference between the two methods bellow: [[PHImageManager defaultManager] requestImageForAsset: …] This will successfully fetch remote iCloud images if your options are correctly configured. [[PHImageManager defaultManager] requestImageDataForAsset:…] This function only works … Read more