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
- Font Asset Creator results bright font colors are not light theme friendly
- Font Asset Creator Font Atlas preview disappears when saved
- When an application is built with Development Build, it results in increase in GUI.Repaint due to DeveloperConsole calls
- Font Asset Creator Font Face dropdown is active but does nothing when clicked if the Font has Include Font Data disabled
- Crash on PPtr<Shader>::operator Shader*() const when Calling Resources.UnloadUnusedAssets() in a specific project
Add comment