We can't trace the exceptions raised in function "AddressableAssetSettings.BuildPlayerContent".

Unity Engine
1

In Addressables 1.18.19, function “BuildScriptBase.BuildData” should use “Debug.LogException” instead of “Debug.LogError” when it caught an exception.

I got an exception which is thrown by functioin “BuildScriptPackedMode.StripHashFromBundleLocation” because of the string in the variable “hashedBundleLocation” didn’t have no "_"s that I modified with my custom BuildPackedMode class.
It was hard to find the cause of error because function “AddressableAssetSettings.BuildPlayerContent” only returns the text of the exception message. Please modify the logging function from “Debug.LogError” to “Debug.LogException” in function “BuildScriptBase.BuildData”'s try-catch scope to make to find the error more easy.

2

Alternatively, the exception thrown in the function “AddressableAssetSettings.BuildPlayerContent” should be returned as the member of the class “AddressableAssetBuildResult”.

3

Hi @yuke_bns thanks for raising this issue! I see that we actually return AddressableAssetBuildResult.CreateResult in a few places that override BuildDataImplementation, but not for all cases. Will create a ticket to see if we can improve this in a future release.

1 Like