Bug The AssetBundle can't be loaded because another AssetBundle with the same files is already loaded.

So I just spent the last several weeks refactoring my project to separate some assets into a separate project from the main project. I build the external addressables and LoadContentCatalogAsync and everything works perfect in editor.
So to test a WebGL build, I build the main project's assets and the other project's assets for WebGL and put both in StreamingAssets under separate directories. Then I build the main engine. I upload it all to S3 and load up the WebGL build, and most of it works until I get that error, then all my local materials are pink (I believe the external shaders are loaded first causing the error on local assets. I bet if I loaded them in reverse order the local shaders would work and external shaders wouldn't).

Code (CSharp):

1. The AssetBundle 'https://*****.s3.amazonaws.com/test/academy/StreamingAssets/AssetBundles/WebGL/miscellaneous_unitybuiltinshaders_0ee8cf1f1746592e1392e2ed48547b63.bundle' can't be loaded because another AssetBundle with the same files is already loaded.

This is a major blocker for us. Are there any solutions?

Unity 2019.1.14f1 and Addressables 1.11.2 (also tested with 1.9.2, same error).

 

Okay, I still think this is a bug that needs to be addressed, but I figured out a workaround. In my main project, I have the default group bundle naming set to

Append Hash to Filename

and in the other project I set it to

Filename

. This seemed to allow all the shaders to load in properly.

Of course this workaround means I now have duplicate shader assets from each catalog, and it also means this won't scale past 4 catalogs (there's only 4 ways to name those auto-generated bundles).

 

What sort of output are you getting from the Check Dupe Dependencies analysis tool?

 

They're built with 2 separate projects, so that tool is useless for this purpose.

 

@TreyK-47 Sorry it took me a while to file the bug report, but it's done now. Case 1268758

 

Issue tracker link: https://issuetracker.unity3d.com/is...e-loaded-when-they-exist-in-seperate-catalogs

 

@TreyK-47

This bug is announced as fixed but it's not. We are using addressable 1.16.15 (we can't use 1.16.16 as it broke loading for us), and we are still getting this error.

We are using addressable for our main game files and modding (we load catalogs using LoadContentCatalogAsync) and any mod that generate a "xx_unitybuiltinshaders.bundle" will not be able to be loaded because of this conflict error. We tried to prevent this unitybuiltinshaders file to be generated, but it seem impossible and any time a builtin shader or texture is used addressable will generate it. We somehow managed to do a dirty workaround to prevent the conflict (disabling CRC check, editing the catalog json and change the path to an unique xx_unitybuiltinshaders), but it still break any builtin shader a modder will use.
Currently we are stuck and we will have to say to our modding community that it's an Unity bug, and that they need to avoid using any builtin shader in their mods to mitigate this issue.

Would be happy if the issue could be opened again, and/or if we could get a workaround to make this work correctly.

 

@KospY I'm not sure how they fixed my original reported issue, but if it's still the same as it was back then, you could try renaming the default group so that each modder should have a unique default group name. I'm not sure how you would go about enforcing that, but that could be a workaround.

 

@ProtoTerminator

I tried to rename, but it throw the same message. I suppose it check the content and if the files in the bundle are same that some already loaded it crash

 

I just saw that addressable 1.17.5-preview added an option to set custom prefix on the unitybuiltinshader AssetBundle! I updated to this version and set the option to "default group GUID" and the problem is gone!!
Whoever worked on this at Unity I just wanted to say thanks to him!

 

What can we do if we use HDRP in our multiple projects?

I have a setup of 3 Unity projects, all 3 using HDRP. In project A I have the main project, which contains some basic assets and I am loading addressable content from a local http server which contains 2 catalogs, created by projects B and C. In project B I have a prefab with a model which uses the HDRP/Lit shader that I export as the content. In project C I have a prefab with another model which uses the same HDRP/Lit shader. Both these projects have been configured as David mentioned, with a custom shader bundle prefix that is unique per project.

Now the thing is that both of them have a dependency to the HDRP/Lit shader, as I can see when analyzing AnalyzeRules->UnfixableRules->[My custom bundle]->Implicit that there is a reference to

Packages/com.unity.render-pipelines.high-definition/Runtime/Material/Lit/Lit.shader

. Because of this, I cannot load both of them at the same time.

I am planning to create multiple projects for Addressable content creation(like projects B and C) and have project A to load the content they create.

 

I'm having the same issue on single project build after upgrading to 1.18.13. If I enable MonoScript bundle, I face the same error but regarding the "monoscript" asset bundle. If I disable it, then I get the error about builtin shaders as above. I'm clearing the build cache and all bundles between every build. Any pointers will be greatly appreciated @davidla_unity

 

@phobos2077 yes, there is definitely a regression in Addressables 1.18.13 that results in that error, on single projects. I reported the issue to Unity with a repro project and posted about it here on the forum: https://forum.unity.com/threads/ass...itybuiltinshaders_xxx-cant-be-loaded.1145711/

 

I'm also being plagued by this error followed by app crash:

Code (CSharp):

1. 2021.07.23 18:16:37.876 15604 15670 Error Unity The file 'none' is corrupted! Remove it and launch unity again!
2. 2021.07.23 18:16:37.876 15604 15670 Error Unity [Position out of bounds!]
3. 2021.07.23 18:16:37.876 15604 15670 Error Unity UnityEngine.StackTraceUtility:ExtractStackTrace () (at /Users/bokken/buildslave/unity/build/Runtime/Export/Scripting/StackTrace.cs:37)
4. 2021.07.23 18:16:37.876 15604 15670 Error Unity UnityEngine.Object:Instantiate<UnityEngine.GameObject> (UnityEngine.GameObject) (at /Users/bokken/buildslave/unity/build/Runtime/Export/Scripting/UnityEngineObject.bindings.cs:271)
5.  

didn't happen in older versions

Tried clearing my Library folder, but it re-appeared again.

 

I also have the "bundle can't be loaded because another AssetBundle with the same name is already loaded" error after updating to the latest version of the plugin. I have a single project. The error appears when I call DownloadDependenciesAsync.

 

If you're experiencing this issue with a single project setup (a "regular" setup) it might be worth looking at the workaround highlighted by @phobos2077 here: https://forum.unity.com/threads/ass...itybuiltinshaders_xxx-cant-be-loaded.1145711/

 

I had the same issue too and desperately tried all sorts of things to fix it. For me it ultimately comes down to missing functionality in Addressables to force a release of all AsyncOperationHandle.

In my tests the problem occurred if an AsyncOperationHandle isn't released of the file that's being updated.

You can find my workaround for this problem here:
https://forum.unity.com/threads/how...-loaded-by-addressables.1121998/#post-7374218

 

This is also causing my grief because I have a web service that provides the bundle and the only difference between a URL for two different bundles are "?" url parmaeters. It appears that unity is lying. Its not there are files named the same IN the bundle (they aren't) but that the url path is being used as a key (without the parameters).

This is not good design. i question using the URL as a key period, but if you are going to do that you MUST include the entire string including any parameters.

It looks like th only way for me to fix this is to completely rewrite the webservice to make the bundle name part of the url itself ...

 

Edit: Update:

Tried that so its not the issue. I have a ccodebase on another machine that doesn't evidence this problem but that codebase has other issues.

My situation is that I am building bundles separately that have prefabs for rendered modles in them,

 

Hey @davidla_unity! Is the issue with using TransformInternalId still happening? We use the TransformInternalId function and are running into this issue with "asset bundles cannot be loaded because one with the same name is already loaded" error.

 

we encounter the error recently. we are using addressables 1.19.19, used WebRequestOverride. when player has bad network and the web request failed, we transform the url to another host.
is it the same issue you mentioned? is there any work around to fix it?