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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment