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
- Create Node Menu is not closing and “NullReferenceException: Object reference not set to an instance of an object” error is thrown when Shader Graph window is closed
- Assert error is thrown when the Editor language is set to one of the experimental ones in an HDRP project
- A BatchDrawCommand is using a pass from the shader “Universal Render Pipeline/Particles/Lit” that is not SRP Batcher compatible
- The Scene does not get rendered in the Player when MSAA is enabled and more than one Camera is used
- Crash on mono_object_get_class when generating Font Atlas of a specific font file
Add comment