Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.5.0
Issue ID
ADDR-1086
Regression
No
[Addressables] InitializeAsync - Unknown error in AsyncOperation
How to reproduce:
1. Open the attached project (AddressablesTest.zip)
2. Build Addressables
3. Move the generated bundles/catalog to http://localhost/Editor/
4. Open "AssetLoader" Scene and enter the PlayMode
Expected result: No errors or an error that explains the issue appears
Actual result: Addressables.InitializeAsync - Unknown error in AsyncOperation error appears
Reproducible with: 2019.3.6f1, 2020.1.0b2, 2020.2.0a3
Reproducible with Adressables Package version: 1.5.0,1.5.1, 1.6.2
Notes:
- Could not test on 2018.4 and lower versions
- Could not test on Addressables Package version 1.4.0 or lower because of dependency errors
- After the `InitializeAsync` call, the error occurs, mentioning the catalog hash file despite the "Disable Catalog Update on Startup" option is enabled
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
https://github.cds.internal.unity3d.com/unity/Addressables/pull/358
Fixed by ADDR-962