Search Issue Tracker
Duplicate
Votes
0
Found in
2019.1.0a6
2019.1.0a7
2019.1.0a8
2019.1.0a9
Issue ID
1099252
Regression
Yes
Crash on mono_method_to_ir when trying to build after the project was created on older version of Unity .NET3.5
To reproduce:
1. Open attached project "1089219.zip"
2. Build for any platform (tested on macOS standalone and iOS)
Expected result: the project is built
Actual result: Unity crashes on mono_method_to_ir mid build
Reproduced on:
2019.1.0a6 2019.1.0a7 2019.1.0a8 2019.1.0a9
Not reproduced on:
2019.1.0a1 2019.1.0a5
Notes:
This only happens when opening a project that was created on an older version of Unity with Scripting Runtime Version .NET 3.5
Newly created project with Scripting Runtime Version .NET 3.5 doesn't cause the crash.
Doesn't crash with Scripting Runtime Verison .NET 4.x
Crashes with Scripting Backend Mono and IL2CPP
The project originally was created on 2017.4.12f1
If trying to build 2017.4.12f1 empty project on 2019.1 everything is fine. It only crashed if editor script was created in 2017.4.12f1 then built with 2019.1
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
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
- Unity Perforce Integration: VCS Connection Active State Fails via CLI with Valid Inputs
This is a duplicate of issue #1103349