Search Issue Tracker
Fixed in 1.7.4
Votes
0
Found in [Package]
1.2.2, 1.5.1
Issue ID
1211014
Regression
No
[Addressables] Local static group bundle name in catalog is changed when build for content update
How to reproduce:
1. Open the attached project ("case_1211014-ContentUpdateTests.zip")
2. Open the repro scene ("SampleScene")
3. Build Player Content (Be sure Addressables is in Packed Play Mode)
4. Navigate to Library/com.unity.addressables/StreamingAssetsCopy/aa/[your platform name]/[your build target]
5. Note the hash of the "defaultlocalgroup" bundle in the directory listed above
6. Modify any of the three object prefabs (Cube, Sphere, Cylinder)
7. Prepare For Content Update
8. Build For Content Update - use the same ".bin" file from step 7
9. In Library/com.unity.addressables/StreamingAssetsCopy/aa/[your platform name]/[your build target], be sure only 1 "defaultlocalgroup" bundle exists and its hash matches the one you noted in step 6
10. Play the scene and make sure all 3 objects still load
Expected results: All 3 objects are loaded
Actual results: None of the objects are loaded, " Unknown error in AsyncOperation" errors are thrown
Reproducible with:2018.4.16f1, 2019.2.19f1, 2019.3.0f5, 2020.1.0a20
Reproducible with package versions: 1.2.2, 1.5.1
Note: On Addressables version 1.1.10, building for content update automatically deletes the old bundle.
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
- "Rendering Debugger" displays incorrect overdraw count when using "Unlit/Texture" shader
- Scene and Game views break when the Editor window is snapped with the Microsoft PowerToys
- Materials do not transfer texture when the "Shader" parameter is changed from "Unlit/Texture" to "Universal Render Pipeline/Unlit"
- [Linux][Vulkan] Crash when opening searchable dialog
- The "Shader error in 'AE/Leaves': "Undefined punctual shadow filter algorithm"" error appears when build completes on a specific project
Resolution Note (fix version 1.7.4):
This appears to have been fixed by our recent work to the Update Previous Build workflow.