Bug (Case 1341792) AsyncOperationStatus (eg CheckForCatalogUpdates) returns "Succeeded" for failed calls

Using Unity 2019.4.20f1 and Addressables 1.18.4.

Calling

Addressables.CheckForCatalogUpdates

where the remote location is not reachable returns

Succeeded

. This most likely affects other Addressables methods too.

Please watch the provided video for a full walk-through.

Reproduce

1. Open project on Windows
2. Open "Addressables Profiles" window and activate "Editor Hosted"
3. Open "Addressables Hosting" window and disable the service
4. Open "Addressables Groups" window and choose "Use existing Build" in the "Play Mode Script" dropdown
5. Click in the Addressables Groups window "Build > Clean Build > All"
6. Click in the Addressables Groups window "Build > New Build > Default Build Script"
7. Press from main menu "File > Build and Run"
8. In the Player press "Check for Catalog Update"

Actual
Game displays "No catalog update available"

Expected
Game displays "CheckForCatalogUpdates failed with status"

 

O:

 

Unity QA was able to reproduce the issue, good job!
https://issuetracker.unity3d.com/is...tionstatus-returns-succeeded-for-failed-calls

 

Bump this. In Addressables 1.20.3, if I call Addressables.InitializeAsync, it will check if the remote catalog is updated. But if I shut down the host which serves the remote catalog and bundles, the UnityWebRequest returns 502 Bad Gateway, but Addressables suppresses this error and the Status of the AsyncOperationHandle returns Success.
So this issue is not fixed. Addressables.UpdateCatalogs also returns Success when the catalog download fails.