Search Issue Tracker
By Design
Votes
0
Found in
2020.3.40f1
2021.3.12f1
2022.1.20f1
2022.2.0b12
2023.1.0a16
Issue ID
UUM-19370
Regression
No
Script Components lose references when importing a package with scripts that have the same name
How to reproduce:
1. Open the attached project “ReferenceBreak.zip“
2. Open Scene “SampleScene“ (Assets/Scenes)
3. Import the attached package “NewAssetVersion.unitypackage“
4. Select the “Test“ GameObject in the Hierarchy
Expected result: Script Components on the “Test“ GameObject are updated
Actual result: The “Test“ GameObject has missing Script Component references
Reproducible with: 2020.3.40f1, 2021.3.12f1, 2022.1.20f1, 2022.2.0b12, 2023.1.0a16
Reproduced on: macOS (12.5)
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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Resolution Note:
The TestScript.cs file existing in the project has a different GUID then the one imported from the .unitypackage. Test game object script components references are no longer found since GUIDs are different.