Search Issue Tracker
Fixed
Fixed in 1.19.9
Votes
1
Found in [Package]
1.18.4
Issue ID
ADDR-2054
Regression
No
Addressables AsyncOperationStatus returns "Succeeded" for failed calls
How to reproduce:
1. Open attached project "AddressablesContentUpdate.zip"
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. Select "Build > Clean Build > All" in the Addressables Groups window
6. Select "Build > New Build > Default Build Script" in the Addressables Groups window
7. Select "File > Build and Run"
8. Select "Check for Catalog Update" option in the Player press
Expected result: Game displays "CheckForCatalogUpdates failed with status"
Actual result: Game displays "No catalog update available"
Reproducible with - 1.18.4 (2019.4.27f1), 1.18.4 (2020.3.12f1), 1.18.4 (2021.1.12f1), 1.18.4 (2021.2.0a21)
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Peter77
Jun 25, 2021 15:28
Related forum thread:
https://forum.unity.com/threads/case-1341792-asyncoperationstatus-eg-checkforcatalogupdates-returns-succeeded-for-failed-calls.1122616/