Search Issue Tracker
Fixed in 2.0.3
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
- Search icon visual quality drops after Unity Theme change on non-primary monitor
- [macOS] Localization files are not created in the Xcode project
- Entity ID for Tile objects is serialized twice which throws an error when using Debug Inspector
- Shader Graph information icon appears below the Property Type Node
- Adding a new Multiplayer Player Tag in the Project Settings window creates a new section in the Project Settings window instead of a popup which is inconsistent with the Editor’s Tags workflow
Resolution Note (fix version 2.0.3):
Fixed by another internal issue: ADDR-3109: [Addressables] Groups build fail when a custom built path is used for an Addressable Group
Resolution Note:
Fixed by another internal issue: ADDR-3109: [Addressables] Groups build fail when a custom built path is used for an Addressable Group