Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.21.8
Issue ID
ADDR-2949
Regression
Yes
Addressables Custom Build and Load Paths are set to NULL when reimporting Scripts
Reproduction steps:
# Open the user’s attached project
# Select “Assets/AddressableAssetsData/AssetGroups/Default Local Group”
# In the Inspector check the ‘Path Preview’
# Reimport the “Assets/NewBehaviourScript” script
# Check the ‘Path Preview’ from the “Default Local Group” again
Expected result: The custom Build and Load paths stay the same
Actual result: The custom Build and Load paths become NULL
Reproducible with: 1.19.19 (2020.3.38f1, 2021.3.9f1), 1.20.5 (2021.3.9f1, 2022.1.14f1, 2022.2.0b5, 2023.1.0a6)
Couldn't test with: 1.19.18 and below (after updating to this version, the issue stops reproducing in all package versions)
Reproducible on: Windows 11
Notes:
- after Build and Load paths become NULL, when building the Addressables Groups the Console throws errors and the building is stalled
- restarting the Editor resets the Load and Build paths
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note:
Fixed by another internal issue: ADDR-3109: [Addressables] Groups build fail when a custom built path is used for an Addressable Group