Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.3
2020.1
2020.2
Issue ID
1237094
Regression
No
An existing Scene gets overwritten when importing a Custom Package
Repro steps:
1. Open the attached project "import-overwrite.zip"
2. Note that the scene "SampleScene2.unity" is empty and open scene "SampleScene.unity"
3. In the Editor, go to Assets > Import Package > Custom Package
4. Import the attached package "SampleScene2.unitypackage"
Expected results: importing "SampleScene2.unitypackage" either creates a new scene with three cubes in it, or it is possible to choose "SampleScene2.unity" in the Import Unity Package window so that an empty scene would be overwritten instead of a filled one
Actual results: it is impossible to choose "SampleScene2.unity" in the Import Unity Package window, the imported package irreversibly overwrites "SampleScene.unity" and instead of three spheres, three cubes are now seen
Reproducible with: 2018.4.0f1, 2018.4.23f1, 2019.3.0a1, 2019.3.14f1, 2020.1.0a1, 2020.1.0b9, 2020.2.0a1, 2020.2.0a11
Notes:
- Importing "SampleScene.unitypackage" changes "SampleScene.unity" back to a scene containing three spheres so that the issue would stay visible
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
In the import window, the iconography + tooltip indicate to the user that the existing file has changed.