Search Issue Tracker
Duplicate
Votes
1
Found in
2017.1.0f3
Issue ID
938208
Regression
No
[iOS] .NET 4.6 build outputs machine.config to mono/2.0 instead of mono/4.0
When exporting an iOS project using the .NET 4.6 experimental support, the machine.config is placed in the mono\2.0 directory, but it should be in the mono\4.0 directory. Because of this, the machine.config file isn't found. This manifested itself in trying to call an https endpoint which failed since the definition of that protocol exists in the machine.config file.
Steps to reproduce:
1. Create a new project
2. Build for iOS
3. Go to Build folder > Data > Managed > mono
Expected behavior: inside mono folder, there is '2.0' folder.
Actual behavior: inside mono folder, there is '4.0' folder.
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
- 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
This is a duplicate of issue #938702