Search Issue Tracker
Fixed in Unity 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
- [TextMesh Pro] Using Ellipsis overflow causes some Emojis to turn into a Square when truncated
- Editor: Assembly icons are not shown correctly.
- [VR]Editor Crashes when exiting the Play Mode if VR support is enabled and a Particle System is emitting mesh instances
- Object with ISerializationCallbackReceiver Interface receives Serialization Callback when it has a private access level
- AssetModificationProcessor.OnWillCreateAsset Callbacks are inconsistent with different Assets
Add comment