Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.2.0b10
Issue ID
1056312
Regression
No
[Windows] Make Mono the default Scripting Backend for Mac Standalone builds
When building on Windows OS to Mac Standalone Scripting backend does not change to Mono by default. Thus the error is shown in Build Settings when build platform is changed to Mac OS standalone.
To reproduce:
1. Open any project on a windows machine
2. Open Player Settings and observe as Scripting Backend is set to IL2CPP
3. Open Build Settings and change from Windows Standalone to Mac OS standalone and notice an IL2CPP error
4. Change Scripting Backend to Mono and notice in Build Settings that the error is gone
Expected result: changing to Mac OS Standalone Scripting Backend changes to Mono
Actual result: you need to manually change Scripting Backend to Mono in order to build to Mac OS Standalone
Reproduced on:
2018.2.3f1
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
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
- Previously deleted “DefaultLookDevProfile“ is present when upgrading the Editor version
- [Ubuntu] UI text and buttons are missing spaces in Unity Version Control > New Workspace window
- "Inherit attribute is not supported" warning is shown but attributes are available in VFX Graph Output and Update blocks
Resolution Note:
We do want to do this, but doing it right is a larger piece of work than just a new player setting. That is why this case is marked as postponed for now.