Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0f1
2018.1.0f2
Issue ID
1032047
Regression
Yes
[Package Manager] Reload from assembly error occurs on updating any package
Reload from assembly error occurs on updating any package through the package manager
Steps to Repro:
1. Open attached or create a new project
2. Window > Package manager
3. Go to In project tab > Ads package
4. Update to the latest version or restore back to an older version
Note: Make sure the package manager UI is updated to 1.9.6 to rollback to an older version of the package
Actual Result:
1. The package updates successfully
2. Observe the console for error
3. Error occurs 2 out of 5 times
Expected Result:
1. The package should update without any errors
Occurring with:
2018.1.0f2, 2018.1.0f1
Working with:
2018.2.0b2, 2018.1.0b13
Environment:
Windows 10 and Mac 10.13
Stack Trace:
Reload Assembly called from managed code directly. This will cause a crash. You should never refresh assets in synchronous mode or enter play mode synchronously from script code.
UnityEditor.EditorApplication:Internal_CallUpdateFunctions()
Comments (4)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
chigolberi
Jul 06, 2019 08:35
When will correct?
JOmoro
Jun 05, 2019 13:09
I get this with Vuforia. Any fix yet?
khrysller
Jun 04, 2019 14:19
This still happening in latest version when I import Unity IAP from Service window
IlisanVlad
May 27, 2019 12:16
I still get it in Unity 2019.3.0a3 after upgrading from unity 2019.1