Search Issue Tracker
Fixed in 5.0.X
Votes
2
Found in
4.5.0f6
Issue ID
613922
Regression
No
Incorrect conditional compilation symbols when building project with "Unity C# projects"
Building a Windows Store App project with "Unity C# Projects" option checked, results in projects are being created with the wrong Unity version in the conditional compilation symbols, for example:
<DefineConstants>...UNITY_4_0_0;UNITY_4_0;...</DefineConstants>
Repro steps:
1. Create an empty project and build a Windows Store App with the Unity C# Project checkbox ticked;
2. Examine the Conditional compilation symbols for Assembly-CSharp-metro-vs2013 and Assembly-CSharp-firstpass-metro-vs2013 projects in Unity project folder;
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment