Addressables content build failure when targeting IL2CPP Linux Server

Unity Engine
, , , , ,
1

When building a Dedicated Linux Server with IL2CPP while on a Windows machine, Addressables builds fail 100% of the time with three errors in the console:

InvalidOperationException: Unable to build with the current configuration, please check the Build Settings.
UnityEditor.GenericMenu:CatchMenu(Object, String[], Int32)

SBP ErrorException
UnityEditor.GenericMenu:CatchMenu (object,string[],int)

Addressable content build failure (duration : 0:00:00.888)
UnityEditor.GenericMenu:CatchMenu (object,string[],int)

This occurs both when trying to build Addressables via the ā€œAddressables Groupsā€ menu (Build ā†’ New Build ā†’ Default Build Script) and when building both Player and Addressables together (File ā†’ Build Settings ā†’ Build/Build and Run).

It is currently impossible to build Addressables with our current version of Unity. This was not happening on our previous version, which was 2022.3.22f1.

Switching to Mono backend lets us build, but we would prefer not to use Mono and expect IL2CPP to be functional.

Versions:
Unity: 2022.3.37f1
Addressables: 1.21.21
Scriptable Build Pipeline: 1.21.24
Sysroot Base: 2.0.10
Sysroot Linux x64: 2.0.9
Toolchain Win Linux x64: 2.0.9

1 Like
2

Same with
Unity: 6.0.14f1
Addressables: 2.2.2
SBP: 2.1.4
Sysroot Base: 2.0.10
Sysroot Linux x64: 2.0.9
Toolchain MacOS arm64 Linux x64: 2.0.3

4

I couldnā€™t get a linux build as well. it seems related to addressables 1.22.2 package comes with unity 2022.3.41. downgraded to 2022.3.39 again and waiting for a proper fix.

you can see that thread and my reply here:

5

Bumping because this is still occurring and has not been acknowledged by Unity.

6

itā€™s a bug
already reported on :

your votes would help.
thanks.

1 Like
7

If youā€™re looking for a temp solution, here is what worked for me:

Iā€™ve manually replaced the Addressables package version in the packages.json, it wasnā€™t in the json but was added as a dependency in the packages-lock.json, so I added this line manually "com.unity.addressables": "2.3.1", and this fixed the build issue for me.

you can check lates addressable version here.

This is not a 100% solution since I didnā€™t test it well and the package manager is still asking me to update addressable to 1.22.2.

1 Like
8

Force updating to 2.3.1 appears to be working at first glance for my project configuration (2022.3.50f1) and the linux addressables build succeeded. Iā€™ll be honest I have no idea what addressables even is so when itā€™s throwing errors when I havenā€™t even touched it before itā€™s annoying. The localization package uses it somehow, I never have.

9

The 2.x and 1.x branches have diverged a little bit, but we try to keep bugfixes on both of them. 1.22.3 is the latest in that stream. Has anyone tried to see if 1.22.3 fixes the issue just like 2.3.1 does?

10

Hey there @timtunity3d !

I can confirm that I have the same issue as Cabskee, and my idea was to update the Unity version to Unity 6 and use the 2.3.1 version, and for me was NOT working. My issue is that I cannot create an Android Addressables build.

This morning I did downgrade the unity version to 2022.3.52f1 and using the 1.22.3 version of the addressables. This is working, Iā€™m able to build for Android after one week.