AddressableAssetsData errors when opening a project on a different computer.

I have a project where both assets and app build correctly on my main Mac workstation but when a partner opens the same project on their end, the Addressable Groups window only shows the "Create Addressables Settings" button even though there's already an AddressableAssetsData folder/file set in the project.

Clicking on "AddressableAssetsData/DefaultObject.asset" brings up this warning:

Detected stack overflow when accessing AddressableAssetSettingsDefaultObject.Settings object.

UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr) (at /Users/builduser/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:187)

Clicking on "AddressableAssetsData/AddressableAssetSettings.asset" brings up this error:

NullReferenceException: Object reference not set to an instance of an object

UnityEditor.AddressableAssets.GUI.AddressableAssetSettingsInspector.OnInspectorGUI () (at Library/PackageCache/com.unity.addressables@1.6.2/Editor/GUI/AddressableAssetSettingsInspector.cs:126)

UnityEditor.UIElements.InspectorElement+<>c__DisplayClass55_0.<CreateIMGUIInspectorFromEditor>b__0 () (at /Users/builduser/buildslave/unity/build/Editor/Mono/Inspector/InspectorElement.cs:521)

UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr) (at /Users/builduser/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:187)

I've now replicated this behavior on another MacOS system using Unity 2019.3.3f1 and Addressables 1.6.2.

What could be causing this issue?

 

I'm running into a similar issue, I can run the project on several different computers with no real issue. But our build server is hitting the same null ref when I click on the AddressableAssetSettings.asset.

Did you ever manage to resolve this issue?

 

I gave up on addressables and went with this:
https://forum.unity.com/threads/simpler-alternative-to-addressables.820998/#post-5844460

 

I see, yeah we are tyring to use the Localization package, so giving up addressables isn't really an option. Thank you for the response though!

 

Hi, was there ever a resolution found to this?

 

I reported the bug today and will post a link here if this gets made into an issue you can vote on.