Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.1.0b1
Issue ID
1130301
Regression
No
Importing Unity Package does not keep track of renames
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “InvalidOperationException” errors spammed in the Console when converting Sample Scene to Sub Scene and Entities Hierarchy window is open
- Using Physics.ComputePenetration on a Capsule collider causes it to sometimes return incorrect value when dragging it through the Mesh collider
- Cinemachine Camera with Position Composer causes visual jitter when following a moving target
- Errors thrown in console when entering Play mode if an object with an Audio Source component is selected
- Editor hangs when a huge mesh is used for CanvasRenderer
Add comment