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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment