Search Issue Tracker
Fixed in Unity 2017.1
Votes
0
Found in
5.6.0f3
Issue ID
896991
Regression
No
[Mono] Not switching to full .NET compatibility for plugins that require it results in unhandled exception in builds
When plugins require .NET 2.0, but .NET 2.0 Subset is selected in the Player Settings, Windows builds result in unhandled exception message on startup.
Steps to reproduce:
1) Open the latest attached project.
2) Build for Windows/macOS.
3) Run the build.
On Windows "Data folder not found - There should be 'test_Data' folder next to the executable." error window appears; the build does not start.
On macOS, the build is terminated instantly.
This exception should be handled properly instead.
Switching to full .NET 2.0 compatibility allows the build to run normally.
Reproduced on:
2017.1.0a4, 5.6.0f3, 5.5.2f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [LWRP][ARKit] Camera feed is not seen when using LWRP on iOS devices
- One Input axis does not work after using Input.ResetInputAxes() while both axes are held down
- [UWP] Build fails when the project folder name has non-ascii character.
- Prefab Asset changes are not reflected inside Prefab Editor when Unity Editor is in the Play Mode
- [Audio] DSP Buffer Size sets to Best performance when pressing trying to set to default
Add comment