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
- Text overlap and is unreadable in Inspector > Terrain Paint Texture after creating new Terrain Layer
- Event "XRInputSubsystem.trackingOriginUpdated" triggers twice when recentering the view
- UITK TextField value is overwritten incorrectly by the converter result when Binding Mode is set to "To Source"
- Out of memory crash when selecting more than 80000 Assets simultaneously
- Test Runner fails to create a script in the active path when selecting a file as the active path
Add comment