Hey how to deal with this? I have android build, that was built with Unity 2018.4.3f1 and installed on device. Then I upgraded to 2018.4.4f1 rebuilt it and got this error when running on device. Obviously CRC of bundles changed and is different from cached ones, but hashes stayed the same.
Error while downloading Asset Bundle: CRC Mismatch. Provided 80fa3744, calculated 6f98367 from data. Will not load AssetBundle
'jar:file:///storage/emulated/0/Android/obb/com.company.product/main.230067.com.company.product.obb!/assets/aa/Android/Android/assets-gui_assets_all_b5609a652ee5a44e2175258937fa7653.bundle'
I have same error when upgrading from 2019.2.7 to 2019.2.8 (before upgrade was working fine):
Error Unity Error while downloading Asset Bundle: CRC Mismatch. Provided 5e94fde7, calculated 7be4dddd from data. Will not load AssetBundle 'jar:file:
Error Unity: Exception encountered in operation Resource(defaultlocalgroup_unitybuiltinshaders_42d35f3191ce5f155b13754293d36a91.bundle): RemoteAssetBundleProvider unable to load from url jar:file:.bundle, result=āRequest abortedā.
Error Unity: Exception encountered in operation Dependencies: RemoteAssetBundleProvider unable to load from url jar:file:/result=āRequest abortedā.
Edit:
I Uninstalled manually app from android device and then build & run from unity again (cleared and rebuilded addresables content) and now i dont see crc error anymore.
Looks like some caching problem after upgrading from older version of unity. Dont know if its related to addresables or not but im using 1.1.4 right now.
I just saw the same issue. Moving from Unity 2019.3.0f6 to 2019.3.3f1. I have a selection of addressable files (all binary) which are present in 6 groups with 3 files in each addressable group.
I saw the CRC mismatch error. Cleaning and rebuilding my data did not resolve the issue. full uninstall on device, cleaning and rebuilding data did not resolve the issue.
The only way Iāve managed to fix it is to rename the group containing the three files related to the bundle that is causing the CRC error, then a clean / rebuild / build to device generates a working build.
Given itās now working, Iāll hopefully leave it there, if you want me to repro and bug it then I probably can.
We had a similar experience, updating from Unity 2019.3.0f6 to 2019.3.4f1. The app could recover though after retrying to load the addressable. @unity_bill Do you have more information about this?
Might be a coincidence, but I never received this error until this week and now I receive it A LOT. Also updated to Addressables 1.8.2 earlier this week. Like I said, might be a coincidence.
Yes using 1.8.2 and 2019.2.15 as well and its happening a lot (was getting it with 1.7.5 as well). I found it happens for me when I switch from streaming assets to remote cdn paths or vice versa. I am doing a lot of testing and rebuilding bundles regularly so itās a huge pain. The only way I found how to fix is to create a new group name that I havenāt used before.
Is this something we can get fixed soon @unity_bill ?
+1 for this bug to be fixed asap, our game is broken now after i update unity and update the addressable package. 2 folder will not be downloaded becaused of crc mismatch
Fix: I have been using Bundle Naming: āFilenameā, switching to āAppend Hash to Filenameā seemed to have fixed it for now but it could just be temporary. Seems like the issue has something to do with the naming of the bundles.
Upgraded our Unity from 2019.3.2f1 to 2019.3.12f1. Got same thing on production. Android. Really need fix. The second time you enter the game - everything is okay.
From what I experienced, it seems that a possible workaround is to manually trigger another download if the first one failed.
Another workaround is, in case of a Unity engine version change in a new build, to clear all the assets cache when the app starts.
If some assets are on a server, then a new version of all the assets (built with the new unity) must be published on that server, in a different folder than the previous one.
This is really annoying because it highly increase the disk space on the server, and it also causes a redowload of all the assets for users who already downloaded them.
Iāve raised those issues in this thread:
But I could not get someone form Unity to clarify how new engine versions are supposed to be handled in regards to Addressables.
I have this issue on some Android devices. The bundle in question is local (part of the obb). Restarting the game only temporarily fixes the issue, it can happen again at any time. For the moment it seems that it is not bound to a specific scene/bundle.
A temporary solution (I do not remember were I found it) is to try loading the scene/asset a second time if the first one fails. This āsolvedā the issue for me.
