Search Issue Tracker
Fixed
Fixed in 1.21.10
Votes
0
Found in [Package]
1.18.16
1.19.19
1.21.9
Issue ID
ADDR-3263
Regression
No
[Addressables] Static bundles are modified if their naming is "Use Filename Hash" when updating build
Reproduction steps:
1. Open the attached project “AddressableUpdate“
2. Open Window > Asset Management > Addressables > Groups
3. In the Addressables Groups window select Build > New Build > Default Build Script
4. In the File Explorer navigate to Library/com.unity.addressables/aa/\{platform you are using}/\{the platform again}
5. Check the “Date modified” column of both files
6. In the Project select “Assets/Cube.prefab” and modify it in any way
7. In the Addressables Groups window select Build > Update a Previous Build and select “\{platform you are using}/addressables_content_state.bin”
8. Repeat steps 4 and 5
Expected result: No files are modified
Actual result: “Date modified” column changed for one of the files
Reproducible with: 1.18.16(2020.3.46f1), 1.19.19 (2021.3.21f1), 1.21.9 (2022.2.12f1, 2023.1.0b7, 2023.2.0a6)
Reproducible on: Windows 10
Note: With 2022 versions and later, after selecting “Update a Previous Build” a window pops up that asks if it could move assets to a different group with Prevent Updates disabled. In that situation uncheck the asset and press the “Continue without changes” button
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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Resolution Note (fix version 1.21.10):
With this fix we have made the behavior consistent between all bundle naming options - this means that bundles marked Prevent Updates will not be built during content update builds regardless of bundle naming option.