Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.19.19
Issue ID
ADDR-2606
Regression
No
Addressables does not remove duplicated assets when their reference is added to other group .asset with a file editor
How to reproduce:
1. Open the user’s attached “TestUnity.zip” project
2. Window > Asset Management > Addressables > Groups
3. Expand "Default Local Group (Default)" and "Test" groups
4. Move the Sphere.prefab from "Default Local Group (Default)" to the "Test" addressables group
5. Exit the Unity Editor
6. In the Default Local Group.asset file (with VS Code or other editor), add the Sphere.prefab reference from the Test.asset file into the Default Local Group.asset file
7. Open the Unity Editor
8. Window > Asset Management > Addressables > Groups
Expected result: Sphere.prefab is present in only one group
Actual result: Duplicated Sphere.prefab is present in both groups
Reproducible with: 1.1.5, 1.19.19 (2019.4.36f1, 2020.3.31f1, 2021.2.15f1, 2022.1.0b11, 2022.2.0a7)
Workaround: Assets > Reimport All, after this is done the duplicated item will be removed
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
There are safe guards in place in Addressables UI to fix this. If files are directly edited to create invalid data, then Addressables cannot automatically fix that. This can happen if someone commits partial changes to source control.