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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment