Search Issue Tracker
Fixed in 2017.3.X
Votes
0
Found in
Issue ID
923404
Regression
No
Built player can not be opened due to error "Failed to load mono", when "Scripts only build" is enabled and mono .NET is changed
Reproduction steps:
1. Create new project.
2. Build project for standalone player.
3. In build settings mark "Development build" and "Scripts only build".
4. Build again.
5. Change .NET version.
6. Build again.
Expected result: There will be error that mono was changed and need full rebuild or built player will be opened correctly.
Actual result: Built player can not be opened. No errors in Unity itself.
Reproduced on: Unity with versions that have .NET 4.6 and .NET 3.5.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment