Search Issue Tracker
Won't Fix
Won't Fix in 1.18.X
Votes
0
Found in [Package]
1.18.4
Issue ID
ADDR-1972
Regression
Yes
Addressables Labels are lost when creating Settings inside of batched Asset operation
How to reproduce:
1. Open the user's attached project
2. In the topbar menu select Bug > Run
3. Select Window > Asset Management > Addressables > Groups
4. In the Addressables Groups window expand the 'Tools' dropdown and select 'Labels'
5. Observe the Addressables Labels window
Expected result: The 'Test' label is listed
Actual result: The 'Test' label is not listed
Reproducible with: Addressables 2019.4.0f1, 2019.4.27f1, 2020.1.17f1 (1.16.10, 1.18.4), 2020.2.0a11 (1.8.5), 2020.3.7f1, 2020.3.9f1, 2021.1.0a9 , 2021.1.8f1, 2021.2.0a17 (1.18.4)
Not reproducible with: Addressables 2018.4.35f1 (1.16.10, 1.18.4), 2020.2.0a12 (1.8.5), 2020.2.7f1, 2020.3.6f, 2021.1.0a8 (1.18.4)
Notes:
- The issue doesn't reproduce if AssetDatabase.StartAssetEditing() is not used
- The issue doesn't reproduce if 'AddressableAssetsData' already exists
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:
The user will need to do AssetDatabase.SaveAssets after adding the label. Otherwise the imported settings object will not include their modifications.
Resolution Note (1.18.X):
The user will need to do AssetDatabase.SaveAssets after adding the label. Otherwise the imported settings object will not include their modifications.