Search Issue Tracker
By Design
By Design in 2023.1.X
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
- 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 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.
Resolution Note (2023.1.X):
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.