UnityWebRequest.GetAssetBundle Fails when a CRC first changes

I've been trying to update my AssetBundle system to use the correct CRCs for files instead of passing 0. However, I keep getting this: Error while downloading Asset Bundle: CRC Mismatch. Provided c7e23ee8, calculated b884e9b0 from data. Will not load AssetBundle

The CRC I'm providing is 100% correct...but it looks like Unity is calculating the CRC on the currently cached bundle and not the new one that I'm pointing to. Once this error occurs and you try again the cache has been cleared and everything works.

This seems like a very serious bug. Has anyone else had this issue?

 

I'm wondering if this is expected behaviour? I am passing version 0 and the correct CRC. I imagine that Unity is deciding to only check the version and not the CRC in some cases? I would have thought changing either of these would cause Unity to re-cache.

I do have a repro project to submit, but if that is expected then I guess that's just how it is. I was hoping to avoid passing the completely arbitrary version number for downloading the manifest bundle since it also doesn't have a hash value. This is something that is still really inconsistent with bundle loading (every other bundle after that can be loaded via Hash128).

EDIT: This checks out. Bumping the version up by one avoids the cache error. However, in the case I mentioned it still resolves itself the second time through if the CRC didn't match (which I would expect to continue failing forever)

 

@KJoanette Did you ever figure this out? I'm having a similar issue.

 

Like @Ben-BearFish I have the similar issue. Have you found a solution ?

 

@Isabelle02 Not that I can recall. We moved onto the Addressables system.