Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0b1
Issue ID
978593
Regression
Yes
MacOS - Importing package by double-clicking fires another Unity instance, on first run after installation.
After installing Unity, on every first instance when user tries to import any package by double-clicking on it, a new instance of Unity gets created.
Note: New instance of Unity only gets created, on first instance after installation.
Steps to reproduce:
1)Install Unity
2) New Project
3)Try to import any package by double-clicking on it.
Workaround:
1)Restart Unity
2)Instead of importing by double-clicking a package externally, import by Assets > Import Package > Custom Package.
Works fine with : 2018.1.a7, 2018.1.a5, 2017.3.0f3, 2017.3.0f1
Regression introduced in : 2018.1.0b1
Environment: Windows. Doesn't happen on Mac.
Frequency: Always
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
- The Hub freezes indefinitely when copy/pasting a lot of characters in the “Set project display name” Hub window since it has no character limit
Add comment