Does this work at all?
Specifically
System.Net.WebClient.DownloadFileAsync( uri, string)
Works beautifully in editor, PC build, mac build… mac editor, fails without ANY notice of error or exception on iPhone/Pad. Fires a DownloadFileCompleted event and writes a 0 byte file.
Anyone know anything about this mess?
Its not reasonable, you are meant to use the corresponding iOS functionality (NSURLConnection) which is how WWW is working, not some funny TCP overlay function.
Though the download there might just fail cause you write to the wrong place because you only have 2 folders to write to on iOS at all
Oh it wrote a 0 byte file perfectly 
Finally got WebClient to throw me an error by using DownloadDataAsync and returning the event args; feeds back HTTP: itself as being unsupported lol… awesome…
WWW it is.
Thank you very much for giving me a strong answer to tell my boss