Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b1
Issue ID
902667
Regression
No
Standalone builds crash on launch: 'Failed to load mono' fatal error when built with 4.6 .NET scripting runtime
Steps to reproduce:
1. Create a new Unity project
2. Open player settings
3. Select 'Experimental (.NET 4.6 Equivalent)' Scripting Runtime Version
4. Build and run
Expected result: app launches
Actual result: 'Failed to load mono' fatal error is thrown on launch
Workaround: restart Editor
Reproducible with 2017.1.0b1
Not reproducible with 2017.1.0a6
Tested on Windows 10 Pro, Version 1703, OS Build 15063.138
Comments (3)
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
tomhsmith
Oct 13, 2017 06:38
oops, meant C# 6 and .NET 4.6
tomhsmith
Oct 13, 2017 06:38
Happened to me today, .NET 6, was building fine yesterday.
Green-Sauce-Games
Sep 30, 2017 02:37
It still happens to me! It seems related to using Null Propagation and .Net 4.6 Script Runtime.