Search Issue Tracker
Fixed in 2018.3
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
- [Build Callbacks] Build is not failing when BuildFailedException is thrown in the PostProcessScene Callback
- [Terrain] The function TerrainData.GetDetailLayer only returns 0 or 1
- [Windows 7] VideoPlayer.Prepare causes a stack overflow crash if Video is loaded from asset bundle
- [WebGL] Mouse input is blocked after a few moves when using Edge browser
- Builds that contain terrain using the Nature/Terrain/Standard shader produce errors when run in headless mode
Add comment