Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
0
Found in
2018.2.0a3
2018.2.0b1
Issue ID
1027798
Regression
Yes
Crash on MonoScript::InitializeAssemblyNameAndScriptType when importing packages
How to reproduce:
1. Create a new project
2. Change the Packages/manifest.json with the one attached to this case
3. Open the project
Actual result: Unity crashes. (gif attached)
Reproducible with: 2018.2.0b1, 2018.2.0a3.
Regression introduced in: 2018.2.0a3.
Not reproducible with: 2018.2.0a2, 2018.1.0f1, 2017.4.1f1, 2017.2.2p3.
Notes:
The crash will happen if manifest.json contains "com.unity.analytics": "exclude", "com.unity.standardevents": "exclude" or "com.unity.ads": "exclude", but it won't crash if it contains only: "com.unity.purchasing": "exclude".
The crash doesn't happen if the project was opened in an older version and Unity window says "[PREVIEW PACKAGES IN USE]".
------------------------------------
fixed in 2018.2.0b5, 2018.3.0a1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment