Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.4f1
Issue ID
1073037
Regression
No
[UWP] Asmdef named similarly will be built with the same Project Guid
Example project contains 3 different assembly definition files named "Assembly.A.asmdef", "Assembly.B.asmdef", and "Assemblyyy.C.asmdef".
Steps to reproduce:
1. Download attached project
2. Switch platform to UWP
3. Build project on the .NET backend with "Unity C# projects" enabled in the build settings
4. Compare assembly .csproj Project GUID (BuildLoc\GeneratedProjects\UWP\)
Expected results: All assembly generated project have different Project GUID
Actual results: "Assembly.A" and "Assembly.B" Project GUID is the same and "Assemblyyy.C" Project GUID is different.
Reproduced with: 2018.3.0a9, 2018.2.5f1, 2018.1.9f1, 2017.4.9f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Add comment