Search Issue Tracker
Fixed in 1.12.0
Votes
0
Found in [Package]
0.4.6 - preview, 1.3.8
Issue ID
1197695
Regression
Yes
AddressableAssetSettings.asset gets modified when assets get modified, even though the configuration does not change
How to reproduce:
1. Open user-submitted project (736949)
2. Make sure 'Verify Saving Assets' is enabled in Unity preferences
3. Change the color of Sample.mat
4. Save the changes via File > Save
5. Attempt to save changes again
Expected result: no changes should have been made to AddressableAssetSettings
Actual result: AddressableAssetSettings has changed since the first save and needs to be saved again
Reproducible with: 2018.4.13f1, 2019.2.12f1, 2019.3.0b10, 2020.1.0a13
Could not test with: 2017.4.34f1(Addressable Assets not yet introduced)
Reproducible with package versions: 0.4.6 - preview, 1.3.8
Not reproducible with package versions: 0.3.5 - preview
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.12.0):
Issue was fixed so that the file should not be dirtied without changes. Fixed in https://github.cds.internal.unity3d.com/unity/Addressables/pull/428