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
- Render Pipeline Converter selected asset counter reports one fewer item when using manual selection
- [Android] [Adreno] [WebGL] A light cookie is not rendered with shader compile error when WebGL build is launched on a device with Adreno GPU
- Rigibody sliding over a flat surface that is made of several GameObjects detects false collisions when Collision Detection is set to "Continuous" or "Continuous Dynamic"
- UI Toolkit Label height is incorrectly calculated when using max-width with percentage value
- Visual Effect Material causes Scene view to update continuously when both Scene and Game views are open, despite "Always Refresh" being disabled
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/