The AsyncOperationStatus.Status are different between first load and second load about addressables-sample

[KeyleXiao]

Sampe1.cs.zip

Yesterday night , I found a bug in Addressables [1.1.10] o_O

When I loading error path , AsyncOperationStatus told me “None” , and try loading again AsyncOperationStatus told me “Failed” , I think the second status is right or the first status is a bug .

What’s the different between first load and second load ? ?

TestCode: Sampe1.cs

The First Click !

Then Click The Button Again ! We can see the “Right Error Info” , Status is Failed .

[KeyleXiao]

I found out the different between first load and second load , in fact when i click the load button , Addressable will execute InitializeAsync (the function is delay execute) . when i click load button again InitializeAsync function are complete . so the AsyncOperationStatus is right.

[KeyleXiao]

[KeyleXiao]

IEnumerator loadRes()
{
    yield return Addressables.InitializeAsync();
 
    var operationHandle = Addressables.LoadAssetAsync<GameObject>(loadPath);

    Debug.Log(operationHandle.Status.ToString());

    if (operationHandle.Status == AsyncOperationStatus.Failed)
    {
        Debug.Log("load failed");
        yield break;
    }
}

if you want to load asset like this, must run [ Addressables.InitializeAsync() ] function first.

Goodnight !

[kirstenpilla]

Hi @KeyleXiao thanks for investigating this! One thing I would suggest is to avoid depending on the value of operationHandle.Status until after the operationHandle has completed. The operation is asynchronous so it's not guaranteed that the Status will always be the same value at a particular frame.