I've been debugging this issue for a while before finding this post. Using the ProxyRepresentation solution works some times, but not always. In my case it will not work if I try to share video content from my app with other apps like Instagram.
I'm starting to think this might be a defect in the SwiftUI ShareLink implementation, because the same URL that fails with ShareLink, will work with the old UIActivityViewController, without having to add values to the plist file and opening up the documents folder for the whole world.
I've been debugging this issue for a while before finding this post. Using the ProxyRepresentation solution works some times, but not always. In my case it will not work if I try to share video content from my app with other apps like Instagram.
I'm starting to think this might be a defect in the SwiftUI ShareLink implementation, because the same URL that fails with ShareLink, will work with the old UIActivityViewController, without having to add values to the plist file and opening up the documents folder for the whole world.
Thanks for reading. Indeed, I encountered some other issues with Transferable API within months after writing this post.
Though how the destination implement as a receiver will also impact the final result, I too believe that the this new API is not robust enough.
For my iOS only app, I plan to use the UIKit counterpart to rewrite the sharing feature, since waiting for Apple to fix those issues is not realistic.