Addressables issue caused by InitializeAsync method

Hello,

I seem to be having an issue with addresables combined with Xbox One game build (Unity 2020.2.1).
Once I launch one of the scenes which relies on addressables (1.17.13), I seem to be getting an error coming from Addressables.InitializeAsync method.
It seems to be failing the Addressables Initialization on Xbox One Dev Kit.
I’m loading the addressables in synchronous manner due to our project structure.

Here is what the errors looks like:

Application.persistentDataPath has been stripped!UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])UnityEngine.Logger:Log(LogType, Object)UnityEngine.Debug:LogWarning(Object)UnityEngine.AddressableAssets.AddressablesImpl:LogWarning(String)UnityEngine.AddressableAssets.Addressables:LogWarning(String)UnityEngine.AddressableAssets.AddressablesImpl:InitializeAsync(String, String, Boolean)UnityEngine.AddressableAssets.AddressablesImpl:InitializeAsync()UnityEngine.AddressableAssets
ddressablesImpl:get_ChainOperation()UnityEngine.AddressableAssets.AddressablesImpl:LoadAssetAsync(Object)UnityEngine.AddressableAssets.Addressables:LoadAssetAsync(Object)AddressablesLoader:LoadSprite(AssetReference)ArenaRef:get_mapPreview()UI_StorySimplifiedButton:Awake()

MissingMethodException: Default constructor not found for type UnityEngine.ResourceManagement.ResourceManager+CompletedOperation`1[[UnityEngine.GameObject, UnityEngine.CoreModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]]  at System.RuntimeType.CreateInstanceMono (System.Boolean nonPublic) [0x00000] in <00000000000000000000000000000000>:0   at System.RuntimeType.CreateInstanceSlow (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Threading.StackCraw
ark& stackMark) [0x00000] in <00000000000000000000000000000000>:0   at System.RuntimeType.CreateInstanceDefaultCtor (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Threading.StackCrawlMark& stackMark) [0x00000] in <00000000000000000000000000000000>:0   at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic) [0x00000] in <00000000000000000000000000000000>:0   at System.Activator.CreateInstance (System.Type type) [0x00000] in <00000000000
0000000000000000000>:0   at UnityEngine.ResourceManagement.Util.LRUCacheAllocationStrategy.New (System.Type type, System.Int32 typeHash) [0x00000] in <00000000000000000000000000000000>:0   at UnityEngine.ResourceManagement.ResourceManager.CreateOperation[T] (System.Type actualType, System.Int32 typeHash, System.Int32 operationHash, System.Action`1[T] onDestroyAction) [0x00000] in <00000000000000000000000000000000>:0   at UnityEngine.ResourceManagement.ResourceManager.CreateCompletedOperationInternal[TO
ect] (TObject result, System.Boolean success, System.String errorMsg, System.Boolean releaseDependenciesOnFailure) [0x00000] in <00000000000000000000000000000000>:0   at UnityEngine.ResourceManagement.ResourceManager.CreateCompletedOperation[TObject] (TObject result, System.String errorMsg) [0x00000] in <00000000000000000000000000000000>:0   at UnityEngine.AddressableAssets.AddressablesImpl.LoadAssetAsync[TObject] (System.Object key) [0x00000] in <00000000000000000000000000000000>:0   at UnityEngine.Ad
essableAssets.Addressables.LoadAssetAsync[TObject] (System.Object key) [0x00000] in <00000000000000000000000000000000>:0   at AddressablesLoader.LoadGameObject (UnityEngine.AddressableAssets.AssetReference _ref) [0x00000] in <00000000000000000000000000000000>:0   at CharacterRef+CharacterSkin.get_prefabNPC () [0x00000] in <00000000000000000000000000000000>:0   at CrowdEntity.Initialize (CharacterRef+CharacterSkin skinRef) [0x00000] in <00000000000000000000000000000000>:0   at CrowdManager.Start () [0x
000] in <00000000000000000000000000000000>:0

Has anyone encountered such error before and has managed to get by it?
I seem to be missing something, as I couldn’t find too much info on this matter.
I have tested newer versions of both Unity and Addressables, but that didn’t fix the problem.

Regards.

2 Likes

Hello!

I’ve encountered the same issue. Did You manage to resolve that problem? Any progress?

Regards.

Bumping this thread, also seeing similar errors

Hi there, sorry for the delayed reply to this thread. I’m not personally familiar with this bug, @robert_galvanic @Marcin_Krokocki would one of you be able to submit a bug report reproducing this issue?