Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.20.0
1.20.3
1.20.5
Issue ID
ADDR-2950
Regression
No
Addressbles.InitializeAsync handle Status returns Success when the remote catalog isn't downloaded successfully
Reproduction steps:
1. Open the attached project “AddressableBugReproduce.zip”
2. Click “Build > New Build > Default Build Script” in the Addressables Groups window
3. Enter Play mode
Expected result: “InitializeAsync Status: Failed” is logged in the Console window because the remote server isn’t reachable
Actual result: “InitializeAsync Status: Succeeded” is logged
Reproducible on: 1.20.0 (2020.3.39f1, 2021.3.9f1), 1.20.3 (2022.1.15f1, 2022.2.0b7), 1.20.5 (2023.1.0a9)
Reproducible with: macOS 12.4 (Intel)
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
Resolution Note:
Due to stability concerns with this behavior change, we're unable to address this right now. The success status is saying the operation successfully completed, even if part of it wasn't able to complete as expected. Initializing Addressables can succeed without downloading a remote catalog. We'll look into ways to make these operations more clear in the future