In another thread (“Why is UnityWebRequest so flaky?”) I asked if anyone knew how to deal with the flakiness of UnityWebRequest. There weren’t any answers, so now I’m looking for a reliable replacement. Is the only alternative the .NET HTTPCLIENT? Any other suggestions?
I’ve been using UnityWebRequest() for a few years now and never seen any flakiness, at least if you properly code for it, make sure it gets Dispose()ed, yield correctly, put the right downloader on it., etc.