Search Issue Tracker

Fixed in 2019.2.X



Found in


Issue ID




Importing Unity Package does not keep track of renames

Asset - Database


Steps to reproduce:
1. Create a new empty Unity Project
2. Set Meta Files to be Visible (Edit > Project Settings > Editor > Version Control > Mode > Visible Meta Files)
3. Import ScriptAOnly.unitypackage from the QA attached project - ScriptA.cs gets imported
4. Import ScriptBOnly.unitypackage
5. Import Unity Package window shows ScriptA - The imported script does contain the line - // Renamed to ScriptB (GUID is unchanged)
6. Import ScriptAandB.unitypackage
7. Observe that Import Unity Package window shows ScriptA twice. Un/tick one will un/tick both. The imported script only contains -// Duplicated ScriptB and renamed to ScriptA (GUID is new). The script that contains - // Renamed to ScriptB (GUID is unchanged) - is missing

Expected result: Importing Unity Package should keep track of renames

Reproduced in: 2019.2.0a6, 2019.1.0b5, 2017.4.21f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.