Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.2.X, 2017.3.X, 2018.1.X
Votes
0
Found in
2017.3.0p1
Issue ID
991154
Regression
Yes
[Regression] UWP project fails to build under .Net Native tool chain in Visual Studio
How to reproduce:
1. Download attached project file
2. Change platform to UWP and Build
3. Open Visual Studio solution
4. Change Configuration to Debug x86
5. In project settings, Build section, mark "Compile with .Net Native tool chain" checkbox true
6. Build on Local Machine
Actual result: App fails to build with error "RHB0011: Internal error: 'pchTypeNameEnd[0] == L'>"at'f:\dd\ndp\rh\src\tools\rhbind\makepdb.cpp:998"
Reproduced with: 2017.2.1p3, 2017.3.1p1
Not reproduced with: 2017.2.0f3
Regression since: 2017.2.0p3
-----------
Fixed on: 2017.4.1f1, 2018.1.0b11, 2018.2.0a4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Active quality level set on a new Universal 2D project is not the default quality level when creating a new project
- Inspector Open button does nothing when navigating to a different folder with a locked asset
- Pre-generated XML serializers fail to deserialize types that use polymorphism when the Player is built with the IL2CPP scripting backend
- Editor crashes with error "Failed to present D3D11 swapchain due to device reset/removed" and Player freezes when rendering a particle system while using modified URP package on DX11
- Crash on Scripting::LogException when async HTTP callback executes after scripting domain teardown
Add comment