We have an issue with remote Addressables on Android using DownloadDependenciesAsync. 98% of the time everything works fine, but occassionaly the download gets stuck at different points of progress. We don’t see any error, just that the progress does not continue to increase anymore. In most cases a restart of the application seems to resolve it (the remaining MB are downloaded).
Overall the download is about 750MB split in 12 groups marked with a “LoadAtStartup” label. MaxConcurrentWebRequests is set to 3 in the AddressableAssetSettings, Bundle mode is set to “Pack Together”.
The problem sounds similar to this one (but didn’t resolve by anything suggested in the discussion):
This is the code we use:
var locations = await Addressables.LoadResourceLocationsAsync(LoadAtStartLabel).Task;
var downloadHandle = Addressables.DownloadDependenciesAsync(locations);
while (downloadHandle.Status == AsyncOperationStatus.None)
{
Progress = downloadHandle.GetDownloadStatus();
await Task.Delay(500);
}
Addressables.Release(downloadHandle);
What we already tried:
Update to Addressables 1.22.3
Reproduce on different devices
Check our CDN for anything suspicious
Check if device has enough space and RAM
Retry mechanism after some time without progress (stuck again immediately, and there seems to be no way to cancel the first download)
Thx for any suggestion what the problem could be:)
bump up this thread, we also encounter the same problem using Addressables 1.22.3, where AddressableUnity.DownloadDependenciesAsync sometimes become stuck and not progress at all
We have tried using the timeout setting for each bundle but the behavior is very random , and we still cant figure out when is the timeout start to count (since the begining of the request or since the request not getting any data)
When we set the MaxConcurrentWebRequests to 1 and a 20s timeout, we can see that the progress is still increasing but the timeout error occur
I think it might be this issue. We’ve been working on trying to track it down. It has been very difficult to get a good repro as y’all have also noticed. If you do come up with a reliable repro please send it along as it could be very helpful to getting a solution.
Just a note about the issue in the tracker - this reporter modified their Addressables code to get more error information, you would not expect to see the “2363380-Download Handler Error” in your stock Addressables.