Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.2.0f3
Issue ID
989286
Regression
No
EditorUtility.ClearProgressBar throws an error and causes Reload Assembly to be called from managed code directly
To reproduce:
1. Open user's attached project
2. Delete first "assembly" file in Assets/Plugins
3. At the top menu bar select Test -> Reproduce Bug
Expected result: New assembly file is generated, no error is thrown and the progress bar is cleared
Actual result: When creating new assembly file error is thrown noting that "Reload Assembly called from managed code directly."
Reproduced with: 5.6.5p1, 2017.1.0f3, 2017.2.1p2, 2017.3.0p3
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
- The Up, Down and other Buttons in a Style Sheet's Inspector unselect items when they are clicked while they are disabled
- Virtual Player remains active and still launches when removed from Additional Editor Instances from a custom Play Mode Scenario
- UI Toolkit Editor Window Creator becomes not interactable and greyed out when a long name is entered
- [Web][iOS] Web Player keeps restarting on launch when Native C/C++ Multithreading is enabled
- "Add Scene to Scenes in Build" pop-up reappears after Scene has already been added and another Multiplayer Editor Instance is loaded
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this issue.