Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
[Asset Importing] .unitypackage file in a project folder can import to the wrong project if multiple projects are open
If you open two projects and you have a .unitypackage file in a project folder of the project you opened most recently, clicking the .unitypackage file to import assets will lead to it trying to import into the other unity project.
1. Create a new unity project.
2. Create a second new unity project.
3. Open both projects. Make note of which project you opened second.
4. In the project you opened second, place a .unitypackage file into Assets folder externally in a file manager. (Do not do it in the editor.)
5. Open the .unitypackage file inside the editor to import it.
Expected Outcome: The package will begin its importing process inside the current project.
Actual Outcome: The window of the project that was opened first will be brought into focus. If you import, it will import into that project instead of the expected one.
Tested and reproducible in 2019.3.0b1, 2019.3.0a12, 2018.4.8f1, 2017.4.31f1
Not a regression.
A .unitypackage file to test this is attached to this project, as well as a .mov file of the issue occuring.
License type: Pro
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- A vertical graphical artifact appears on Android Player when clearing Z & Stencil Buffer and running with OpenGLES3 Graphics API
- Player crashes when built with IL2CPP Scripting backend
- TextMeshPro package throws multiple Shader errors when importing TMP Essential Resources
- Package Manager search text field has no validation and leads to Editor freezes
- PlayerLoop.SetPlayerLoop() function is ignored when playing game in Player