CRC Mismatch

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.

Code (CSharp):

1. Error while downloading Asset Bundle: CRC Mismatch. Provided 80fa3744, calculated 6f98367 from data. Will not load AssetBundle
2.  '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'

Is this the case? https://forum.unity.com/threads/bug-retry-load-with-failed-crc.693751/

Thanks

 

Bump, is this a bug? Or is there a way to detect this and redownload?

 

this feels like a bug, and yes, it does seem to be the same thing as the linked post. We'll look into it

 

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<IAssetBundleResource>(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.

Anyone else?

 

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.

 

Same problem here with Unity 2019.3.13f1 and Addressables 1.8.3.

 

Same here. 2019.3.13f1 / 1.8.3. Blocking us as of now

Error while downloading Asset Bundle: CRC Mismatch. Provided f19b9f5e, calculated d86862cf from data. Will not load AssetBundle 'https://our-cnd-url.net/StandaloneW...s_all_a7d1a935ac06a85a5456d7b35aff896e.bundle'

 

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:
https://forum.unity.com/threads/how-to-upgrade-unity-without-breaking-addressable-bundles.846907/
But I could not get someone form Unity to clarify how new engine versions are supposed to be handled in regards to Addressables.

 

Same problem on 2019.4.0f1.

Any news/fixes about that?

 

I'm running into this same issue myself , happy I'm not alone, it's a major blocker to our pipeline for our gmae.

 

[Unity 2018.4.18; Addressables 1.10]

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.

 

Have this issue in Unity 2019.4.5, Addressables 1.13.1.

Upgraded recently from 2019.2.17. I'm using only local bundles.

Trying now to disable CRC + CRC for Cached Bundles as it is currently only affecting 1 Group (Single scene inside)

 

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.

 

Hi, using Unity version ([UnityEngine.Application.unityVersion]) as part of BuildPath and LoadPath solved the issue for us.

 

This issue happens to me only on Android devices while using Addressables. On iOS it works nice, except for a very few rare occasions... Does anyone know why the Android platform might be causing this specific issue?

 

You mean to write: [UnityEngine.Application.unityVersion] instead of [BuildTarget] at the end of our path? If we are using both Android and iOS, will it generate a problem?

 

No, you write both.

[BuildTarget]/[UnityEngine.Application.unityVersion]

or

[UnityEngine.Application.unityVersion]/[BuildTarget]

 

Hitting this in Unity 2019.4.9f1 and deploying to webgl.

I did a clean on the asset build pipeline. I deleted everything on Azure's blob. Re-uploaded addressables there.
Deleted everything on the ftp and re-uploaded a fresh build.

I don't get any errors when I use Play Mode use existing build in the editor. But I do get the error in Webgl running in Chrome.

Only 1 of our 4 bundles has the error.

 

The problem is still there in Addressables 1.8.5, unfortunately :/

Gonna try the "retry download" solution...

Can you please, elaborate this? I am new to Addressables. Should I set up remote and addresses to <custom> to achieve this solution? Thanks.

 

I've just found this happened in a test run on our CI machine - so it's happened once and I don't have a repro. We just use local bundles, no downloads.

Reading this thread, it doesn't sound like anyone has logged a bug with Unity, so they won't be looking at this. Can someone with a solid repro log a bug and mention the bug number here?

 

Yeah this would help us a ton! I'll let the team know about this also!

 

Thanks @Shaunyowns and @DavidUnity3d ! If we get a proper repro I'll be sure to log a bug, but for now it's just one of the many random failures we're trying to stamp out.

We're on 1.15.1 of Addressables, so pretty recent.

Platforms being built on CI are Windows Standalone, PS4, Xbox One, and Switch.

If this becomes a more noisy problem we'll try disabling CRC checking - though will that just allow problems to manifest later on in the run?

 

Unity 2020.1.2 ,addressable 1.16.1, build platform windows, same problem.
But Android is OK.
Is a bug or something?

 

Yeah. At the remote and local build path you add that at the end of your address. Unfortunately, didn't work for me

 

I think I have the same issue mentioned here and I'm just wondering if I'm using it wrong?
I'm using addressable version 1.15.1
Going from Unity 2019.4.10 to 2019.4.12
Building for Android

I'm loading one of the groups from the remote and it's marked as "Can Change Post Release" with Append Hash to Filename.

When I build the bundles with unity version 2019.4.12, the bundles are different and it updated the version in the file.

I added an image to show the difference in the file.

The problem is that this file still has the same hash as it did when building with unity 2019.4.10.
What would happen now is that my Unity 2019.4.12 build is not able to load the files created with .10 and my 2019.4.10 build that is already on the store is not able to load the new bundles!

It throws a CRC mismatch error:
2020-10-21 09:39:25.366 16690-17162/? E/Unity: Error while downloading Asset Bundle: CRC Mismatch. Provided 3b0ad501, calculated ad1ae218 from data. Will not load AssetBundle 'https://cdn-files-accept.gop3.nl/ad...kdrop_50119efb6ea3e4834683b077f6b09ec6.bundle'2020-10-21 09:39:25.374 16690-17103/? E/Unity: Exception encountered in operation Resource<GameObject>(r1a2l0_backdrop.prefab), status=Failed, result= : Unable to load dependent bundle from location Assets/com/youdagames/gop_tt/client/resources_moved/ex_assets/SaloonBackdrops/r1a2l0_backdrop.prefab

Now, I have solutions.
1 : Disable CRC in the new build and not update the files on the remote.
But I would really want to keep CRC I think?
2: Do the solution @ProtoTerminator suggested and add the unity version in the remote load and build paths but this would make it so every user downloads the bundles again when we update the engine.

So is this supposed to work like this? @DavidUnity3d or is it a bug.. because this is kinda weird right now?

 

Hi all,

Just to provide more info about this issue. We are suffering this issue as well but we are not using addressable assets so I think it could be related to the core of asset bundles feature. We have our custom solution to deal with asset bundles and we persist the CRC of every bundle and at download we pass the CRC as parameter. In 2018.4.25 works perfectly but as soon as we ported our project to 2019.4.13 we started to suffer this problem.

Regards

 

Hey @DavidUnity3d
This is extremely strange, to be honest. what is the benefit of having the hash be the same if the bundles do not work across different unity version? We tested this and I'm sure that when we tried to load asset bundles from 2019.4.12 with a build from 2019.4.14 it did not work.

 

@BenHymers
We also had random CRC Mismatch issues on our CI machine.
It turned out that one of our RAM sticks was faulty and would effectively corrupt the bundles.

 

CRC Mismatch too，unity2019.4.15f1c1 A ddressable 1.16.10 Android

 

I have this error when running in Unity Editor.

Error while downloading Asset Bundle: CRC Mismatch. Provided 603c3b5c, calculated 5826517c from data. Will not load AssetBundle

Unity 2020.2.2f1

 

Also having some of these appear for me. It is happening in the WebGL version for players.

Unity version: 2019.4.19f1
Addressables version: 1.16.16

 

We have been running into CRC mismatch a lot here as well and our fix (before seeing this post) was also to disable CRC checks, which improved our experience a lot!

Can you describe briefly some of the issues this could introduce and how likely they may be, and which situations?

I am just a little unsure how the CRC check may benefit us and if we even need it at all.

 

You don't need CRC checks in WebGL because the browser already has it built in. CRC checks just slow it down for no reason.

 

CRC Mismatch too...

Steps:
1) (Clean Build -> All) + (New build -> Default build script).
2) Build standalone application A.
3) Reopen unity (important!).
4) (Clean Build -> All) + (New build -> Default build script).
5) Build standalone application B.
6) Upload bundles to server (url/[BuildTarget]).

On application A: error, crc mismatch.
On application B: all ok

File has changes. This is normal?


Without reopen unity the files are the same.

 

I am also having the same problem here with my Android build.
I built the addressables with my machine with Unity 2019.4.17f1, however the game is being built with UCB to the last LTS version, which is 2019.4.22f1.

I will try to update my local unity version and build all again to see if it works.

 

Hi there, any suggestions？
We meet this problem with Android build too, in Unity 2019.3.4f1 and the version of addressables is 1.16.7.
Then we upgrade it to 1.16.16, but still the problem exists.
Well I guess is might be related to reopen Unity, cuz I had some tests, with same content of assetgroups and assets, after reopen the Unity and BuildPlayerContent, the crc of which bundles has changed.
btw, those bundles were scenes, and only scenes bundles had crc changed (for me).

 

Have that issue also, when I start my build, it will download, complaint about crc mismatch, and once I restart the player, it work without complaining

 

I'm also often encountering that CRC mismatch issue when building/testing for Android

EDIT: when this happens, the easy fix is to update Bundle version and/or code and to build again

 

If scene doesnt changed but only some of assets used in the scene changed. crc mismatch issue happening. If you make some changes to scene's itself from unity editor, the problem is gone.

This is the reason that why unity devs. didn't reproduce this issue yet.

If you change any scene dependencies. you need to make some even unnoticable changes on scene's itself to prevent this issue until a fix released.

 

I am having this error at the moment and am unable to fix it. The problem occurred after updating the Unity version and building new bundles. I removed all bundles from the server and downloaded new ones and clients started getting this error. To fix the situation, I tried to disable the CRC check, collected new bundles and uploaded them to the server and also updated the build - does not help.



Error while downloading Asset Bundle: CRC Mismatch. Provided 6ca615e1, calculated 5aa7f2fc from data. Will not load AssetBundle

 

We are also experiencing this issue. It was fine for a few days, and then suddenly today, old releases were getting the CRC issue. Tried uploading old addressables, fresh install of app but that didn't solve the problem. Only a new build seems to work, old releases get numerous errors, first one being CRC.