[expo-media-library] Add isNetworkAsset flag to ios

[jarvisluong]

Why & How

Mentioned in #8541

Test Plan

With a real device, make huge asset so that iCloud delete the local version, then open the test app and select that asset

[jarvisluong]

@byCedric @tsapeta

One thing I just noticed that the key PHImageResultIsInCloudKey and PHContentEditingInputResultIsInCloudKey is only present if we make networkAccessAllowed to NO like in here:

expo/packages/expo-media-library/ios/EXMediaLibrary/EXMediaLibrary.m

Line 407 in e166a8d

options.networkAccessAllowed = YES;

However, setting that flag to NO won't download the iCloud asset to the device, so we would need to fetch first with NO value, then again with YES for the asset to be downloaded. Do you think we should go with this solution?

Otherwise, we would need to make the method getAssetInfoAsync to be more configurable in JS side (in order to dynamically specify PHContentEditingInputRequestOptions and PHVideoRequestOptions

[lukmccall]

Otherwise, we would need to make the method getAssetInfoAsync to be more configurable in JS side (in order to dynamically specify PHContentEditingInputRequestOptions and PHVideoRequestOptions

I believe that is the best option - I don't like making two calls for the asset.
Nevertheless, please update the documentation ;)

[tsapeta]

Yeah, I agree that making it more configurable is a good idea 👍

Does it also mean that PHContentEditingInputResultIsInCloudKey is not available when networkAccessAllowed is set to YES? What's its value then? We need to make sure it's not nil because it would throw an exception when converting it to JS object. We would need to use [NSNull null] instead of nil.

[jarvisluong]

Yeah, I agree that making it more configurable is a good idea 👍

Does it also mean that PHContentEditingInputResultIsInCloudKey is not available when networkAccessAllowed is set to YES? What's its value then? We need to make sure it's not nil because it would throw an exception when converting it to JS object. We would need to use [NSNull null] instead of nil.

You are right, the value will be nil

[jarvisluong]

I started working on an updated PR, hence closing this one