Addressable cannot be used due to "SBP error exception"

Questions & Answers
1

The following error message is displayed when test play of the game is started.

InvalidOperationException: Unable to build with the current configuration, please check the Build Settings.
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)

SBP ErrorException
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

In my project Addressable there is only one group where assets are registered.
If I unregister all assets in that group and then run a test play of the game, I can start it without any errors.
If I register any new assets to the group, I will not be able to start test-playing the game again.

If no assets are registered to the group, it is possible to build and test-play Addressable.
If I register any assets to the group, it will not be possible to build Addressable and test play will not be possible.
Errors that occur when the build of Addressable fails are as follows.

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.09)
UnityEditor.GenericMenu:CatchMenu (object,string[],int)

Deleting the Addressable folder, re-installing Addressable with the latest version and generating a new configuration does not change the symptoms.
The version of Unity is 2022.3.10f.1.
Updating the Unity version to 2022.3.12f.1 does not change the symptoms.

Help me.

3

note: since it’s not too visible at first, would like to repost original poster’s solution as he commented to his post:

Resolved. This was a very boring mistake. There was a mismatch between the values for ‘File > Build Setting > Comporession Mode’ and ‘Addressable > Addressable Asset Group > Advanced Option > Asset Bundlee Comporession’. I don’t know how I got into this situation, but, well, I must have done something. – Kuroco965 Nov 4, 2023

I am having the same problem right now with unity update from 2022.3.39f1 to 2022.3.41f1 with targeting Linux platform on a macbook silicon device. This post is useful since it seems for me as well, addressables are the main issue here as the addressables package updated with unity update. removing addressable group solves the issue for me, and recreating didn’t solved for me. also compression settings for addressable group didn’t solved for me as well.

tldr; 2022.3.41f1 seems broken now targeting Linux with addressables, I couldn’t solved, will try to downgrade back to 2022.3.39f1 for now.

post-downgrade edit: downgraded to 2022.3.40f1 as it doesn’t include addressables package update, it seems fine for me and @amynox.

2

Solved!
My mistake!