Search Issue Tracker
Won't Fix
Votes
1
Found in
5.5.0p3
Issue ID
875643
Regression
Yes
Prefab script references missing from an imported package
Steps to reproduce:
1. Create new Unity project
3. Import Easy_Save_v2.7.1p1 package
4. Notice that both prefabs in EasySave2/AutoSave lost their script references
Expected result: script references should not be missing when the package is imported
Note: When the project is imported in 2017.1.0-5.5.x the following error appears - error CS1704: An assembly with the same name `UnityEngine.UI' has already been imported. Consider removing one of the references or sign the assembly
C:/Program Files/Unity 5.5.1f1/Editor/Data/UnityExtensions/Unity/GUISystem/UnityEngine.UI.dll (Location of the symbol related to previous error)
Reproduced in: 2017.1.0a4, 5.6.0f3, 5.5.1f1
Working in: 5.2.3f1, 5.3.6f1, 5.4.2f1
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
Add comment