Hello everyone, I have some questions about asset bundles and how they're cached. Maybe I just missed the point and one of you will be able to enlighten me. Isn't a previous versions of an asset bundle supposed to be deleted from the cache when a new one is downloaded ? After a rapid test in the editor, it seems that when I download and cache a new version of an asset bundle (same url, different hash), the previous version is kept in the cache. This seems useless and will fill the cache with outdated data. On mobile where disk space can quickly become an issue, this is very unpractical. What's the point of BuildAssetBundleOptions.AppendHashToAssetBundleName ? At first I thought it was nice because the bundle filename included automatically a sort of versioning info. But then, I realized that because the bundle filename changed everytime, each update of a bundle would just sit next to the previous version in the cache. Because there is no way of deleting a single bundle from the cache, you're left with only two options : - Clean the whole cache every time a single bundle is updated, which is kinda stupid. - Wait for the cache to be full so that the oldest bundles are removed, which also sucks. Why can't you delete a cached AssetBundle from the cache ? All those problems could be easily fixed if we could delete an assetbundle from the cache ourselves. Now that Caching.DeleteFromCache is deprecated and doesn't do anything, there is no way to do that anymore. What if you had an asset bundle that it not used anymore ? It's gonna sit in the cache for as short a time as the Caching.expirationDelay value you're willing to set or as long as the cache is not full. Is there a reason this was deprecated and not replaced by anything ?