Search Issue Tracker
Fixed
Fixed in 1.21.10
Votes
0
Found in [Package]
1.21.8
Issue ID
ADDR-3233
Regression
Yes
Content Update Builds modify the static bundles when their naming has "Use Filename Hash" set
How to reproduce:
1. Open the attached “IN-34077.zip” project
2. Open the Addressables Groups window (Window → Asset Management → Addressables → Groups)
3. Make an Addressables Groups Build (Build → New Build → Default Build Script)
4. Modify the “Cube” Prefab in any way
5. Update the Addressables Groups Build (Build → Update a Previous Build)
Expected result: Nothing of note happens and Addressables get built
Actual result: Addressables build shows as modified and an error “Addressable content pre-build failure : Update a Previous Build” is thrown
Reproducible with: 1.20.3 (2020.3.46f1), 1.21.8 (2020.3.46f1, 2022.2.10f1, 2023.1.0b7, 2023.2.0a5)
Not reproducible: 1.18.19 (2020.3.46f1), 1.19.19 (2021.3.20f1), 1.20.0 (2020.3.46f1)
Reproduced on: macOS Ventura 13.1 (Intel)
Notes:
- The 2021.3 stream has the 1.19.19 version as the latest available to use, so verification, if the issue is reproducible, is not possible
- 2022.2 stream might reset the “Play Mode Script” setting, change it to “Use Existing Build” if it does.
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
With this fix, bundles are treated identically regardless of their bundle naming option. This means that in content update builds bundles that are marked Prevent Updates will not be built, which is in line with the other bundle naming options