Search Issue Tracker
Fixed
Fixed in 1.18.11
Votes
0
Found in [Package]
1.16.19
Issue ID
ADDR-1999
Regression
No
[Addressables] Content update fails when assets are at the root directory in the Addressable Groups
How to reproduce:
1. Open the user's attached project and Entry scene
2. Select Window/AssetManagement/Addressables/Groups and Build/New Build/Default Build Script
3. Build and Run the project (observe the view and close it)
4. In the Project window, open UI Canvas prefab and move the Bottom GameObject down (or make any other modifications)
5. In the Addressables Groups window, select Tools/Check for Content Update Restrictions and select the addressables_content_state.bin
6. In the Content Update preview window, select Apply Changes
7. In the Addressables Groups window, select Build/Update a Previous Build
8. Enable Addressables hosting
9. Reopen the Build and observe the view
Expected result: UI Canvas is rendered
Actual result: nothing is rendered
Reproducible with: 1.16.10 - 1.16.19 (2018.4.35f1, 2019.4.27f1, 2020.3.10f1, 2021.1.8f1, 2021.2.0a18)
Could not test with: 1.17.13 - 1.18.4 (because of the existing bug: https://issuetracker.unity3d.com/product/unity/issues/guid/ADDR-1942)
Note: Not reproducible when assets are inside of a folder in the Addressables groups
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note:
Appears to be fixed in 1.18.11
Resolution Note (fix version 1.18.11):
Fixed in: Addressables 1.18.11