Bad Address results in Exceptions (and not just a Status == Failure)

We're having the following issue with trying to find an addressable that doesn't exist. The below very simplified example does what you expect. Returns status == Failure which is great. The problem is, in the process, it's also giving us 4 different exceptions. Any thoughts?

Code (CSharp):

1.  
2. private void BadAddressTest()
3. {
4.     Debug.Log("Bad Address Test");
5.     Addressables.LoadAssetAsync<GameObject>("bad_address").Completed += OnLoadDoneTest;
6. }
7.  
8. private void OnLoadDoneTest(UnityEngine.ResourceManagement.AsyncOperations.AsyncOperationHandle<GameObject> obj)
9. {
10.     Debug.Log("OnLoadDoneTest" + obj.Status);
11. }
12.  

And see attached screen grab for all the exceptions.

 

Maybe surround the LoadAsset call with a try catch so the execution will not be interrupted?

 

Yah we're currently doing that. But it feels like these exceptions shouldn't be thrown in this case. Wondering if this is an indicator of something problematic with our setup or something more sinister.

 

[Unity 2018.4.18; Addressables 1.6.2]

I have been replacing a lot of Resources.Load calls with Addressables.LoadAssetAsync and I am getting errors in the console whenever the key is invalid. I cannot silence it with try catch.

I know I am giving a bad path but I want to try anyway and my console is being spammed with hundreds of errors which hides the real errors.

Is there a way to have the addressables system handle it silently just like the resources system does?

 

In the top level Addressable settings, uncheck

Log Runtime Exceptions

.

 

Thanks a lot ProtoTerminator.

The error do not appear in the console anymore.

 

Sorry for the delay. I am on 1.6.2 Addressables. And 2019.3.1f1

I'll try the uncheck of Log Runtime Exceptions. Thanks ProTerminator!