Bug Addressables not loading in build

I reverted to 1.16.15 and updated the localization système to 0.10, and it seems to work better, for the localization at least.
(I'm in Unity 2020.2.1f1)

 

Thank you for taking a look at this!

I tried to create a repro but couldn't. I copy pasted the same exact script and prefab loading, but I can't get it to break.
My guess is that it is some sort of asset-related issue when it is building the catalog or bundle. I have 3+ GB of assets, so I'm really not sure what is breaking it.

Also: there is no error.
I am using InstantiateAsync, and the callback does run, but the Result is null.

Code (CSharp):

1.             var a = prefabAddressable.InstantiateAsync();
2.             a.Completed += (c) => {
3.                 Debug.Log(c.Result.name);
4.             };

At runtime, the Debug.Log throws null, as c.Result is null.
Without the Debug.Log, it's a silent error: no error is thrown, but no gameobject is instantiated.


Also, it doesn't matter what I put as prefabAddressable.
I tried creating a new simple basic cube prefab addressable, but that still breaks it.

Everything works perfectly in the Editor, even with use built groups setting. And it works with Build and Run--super weird.

 

Hopefully, this issue gets solved soon.

 

Heya, we're suffering from the same issue. I made a diff of the catalogs of a working (addressables 1.16.15) and non-working (latest 1.17.4-preview) build and I found out that the bundle paths in the m_InternalIds array are totally different. Whereas the paths from 1.16.15 point, for example, to "{UnityEngine.AddressableAssets.Addressables.RuntimePath}/StandaloneWindows64/fonts_assets_all.bundle", the paths from 1.17.4-preview point to "Library/com.unity.addressables/aa/Windows/StandaloneWindows64\\fonts_assets_all.bundle". I assume this breaks inter-bundle dependency management and thus assets can't be loaded correctly anymore. I'm just puzzled that there are no errors raised that fail to find bundles etc.

I had also diffed the source code of the involved packages and the only thing that struck me was the handling of "append hash" bundle naming that changed from one version to the other. We don't use it, so maybe this change broke how final dependent bundle paths are generated.

 

Submitted a bug report (case #1312333) with a really small repro project, uploaded it here as well in case the unity bug reporter swallowed the repro project once again: https://github.com/zsoi/AddressablesBrokenRuntimeBundlesRepro

 

@davidla_unity I also found the same issue reproducible even with Addressables 1.16.15 with SBP 1.15.1 in Unity 2020.2.x. The error does not happen with Unity 2020.1.x and earlier using Addressables 1.16.15 with SBP 1.15.1.

The error appears to be related to specific assets. To troubleshoot, I added debug logging in
the method CreateSubAssetLoadInfo in GenerateSubAssetPathMaps.cs to inspect assetInfo and subAsset to catch the bad index. Once I was able to identify the problematic asset and its dependencies, removing it from addressables will make the build succeed again.

Nothing is different with the assets between upgrades of Unity and Addressables and everything works in the Editor and play mode. Just fails to get the proper index in CreateSubAssetLoadInfo.

Edit: MacOS Catalina, build fails for both Android and iOS platforms.

 

I have encounter the same issue using Adressables 1.16.15 in a Linux player build (mac and windows seems to work fine).

Mac OS 10.15.7
Unity 2020.2.1f1
Adressables 1.16.15
Linux build

I will try 1.16.6 and the preview versions to check if one of the solves/changes the issue for me.
Update: I tested 1.16.6 and 1.17.4 and it did not fix it

 

I managed to solve the issue. Using 1.17.4 I got an additional Exception in the debug output:

Exception encountered in operation Resource<ResourceManagerRuntimeData>(settings.json), status=Failed, result= : Invalid path in TextDataProvider : '/home/twindrums/server-headless-0.00.01/server-headless-0.00_Data/StreamingAssets/aa/settings.json'.

It was missing the settings.json file. The project uses the remote buildpath and the build process does not create a settings.json file in the RemoteBuildPath (I used the one from the LocalBuildPath).

 

I'm having problem with this also. My build compiles correctly using the https://game.ci/ github actions, but when the game tries to initialize addressables, an error pops:

RuntimeData is null. Please ensure you have built the correct Player Content.

 

Turns out you can't have an aa directory in StreamingAssets, since the AddresablesPlayerBuildProcessor will remove it. *sigh*

Can someone explain to me, why one needs the settings.json file for loading addressables from a catalog? What exactly is kept in that file? And why is it not handled correctly when building for a remote path?

 

Upgrade from unity2020.1, addressable 1.16.15 => unity2020.2.3f1, addressable 1.16.16, clear all cache, rebuild addressable, build windows player, when game start, addressable fails to load,

Exception encountered in operation Resource<IAssetBundleResource>(logo.bundle), status=Failed, result= : Invalid path in AssetBundleProvider: 'Library/com.unity.addressables/aa/Windows/StandaloneWindows64\scenes_scenes_scene/logo.bundle'.

Seems like addressable is using local build path instead of local load path in player.


Edit:
opened up catalog.json

"m_InternalIds":["Library/com.unity.addressables/aa/

seems all internal ids have been replaced by local build path. may be a bug of SBP 1.15.2?

 

Same issue here after updating to 1.16.16 (and SBP 1.15.2). This issue didn't exist in 1.16.15 with SBP 1.15.1 as I just used that yesterday.

EDIT: I downgraded back to 1.16.15 (plus cache cleanup) and now it's all working again.

 

Addressables 1.17.5-preview did not fix this other issue I'm having.

 

Issues in our production project have been solved for us with this update as well, thanks!

 

Hello! The problem is present in Unity version 2019.4.20f1, Addressables package 1.17.5-preview.

blob:file:///5f3b9122-284a-43b8-8c5d-377ce5e98f1e:8 Exception encountered in operation Resource<ResourceManagerRuntimeData>(settings.json), status=Failed, result= : TextDataProvider unable to load from url file:///D:/!OpenSpace/Development/BuildResult/StreamingAssets/aa/settings.json, result='HTTP/1.1 0 Unknown HTTP status'.
(Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)


_JS_Log_Dump @ blob:file:///5f3b9122-284a-43b8-8c5d-377ce5e98f1e:8
blob:file:///5f3b9122-284a-43b8-8c5d-377ce5e98f1e:8 RuntimeData is null. Please ensure you have built the correct Player Content.
(Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)

The error occurs in the generated application. UnityInstance just doesn't see built-in Addressables. Cleaning and building Addressables does not affect the result. Below is a link to a simple project where you can reproduce the error while building your application. Everything works in the editor, there is localization.
https://drive.google.com/file/d/19qxbMwwHaQNL5xgUiTp9fDAUgwI39Xts/view?usp=sharing

 

it seems that in some cases the browser does something wrong
https://forum.unity.com/threads/no-locales-were-available.1059779/

 

I am still getting a null type in the uniqueTypes list that is getting built in ExtensionMethods.ExtractCommonCacheData.

This does not occur in Unity 2019, but does in 2020; even with the latest (1.17.6-preview) addressables.

 

Unity 2019.4.8.f1 with 1.16.15 I had addressables issues that midproject surfaced. I just updated to 1.17.6-preview and made a working build

 

i get this bug sometimes, like few times a day, i ahve to rebuild and recompile and then it works

 

Using Unity 2019.1.14f1 and Addressables 1.17.13, bug still happening:

Exception encountered in operation Resource<ResourceManagerRuntimeData>(settings.json), status=Failed, result= : Invalid path in TextDataProvider : 'C:/Users/etc/Downloads/Gatch v4.20210320/Gatch_Data/StreamingAssets/aa/settings.json'.

Will try to update the project to the latest LTS and see if the bug is solved there.

 

Bug fixed after I updated the project to Unity 2019.4.22f1.

 

It's my first time working with Addressables and I faced the same problem when exporting both for Android and Windows.

However, updating the package to version 1.17.15, as @davidla_unity suggested, solved the issue!

I'm using Unity 2019.4.20f1 at the moment.