Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.4
2019.3
2019.3.7f1
2020.1
2020.2
Issue ID
1232169
Regression
No
Building the project with IL2CPP fails when Visual Studio 2019 16.5.4 is used
How to reproduce:
1. Open the attached project named "Case_1232169"
2. Open the Build Settings
3. Check if the "OpenThis" Scene was included and build the project. Target platform - Windows_64
Expected result: Build succeeds
Actual result: Build fails
Reproducible with: 2018.4.23f1, 2019.3.14f1, 2020.1.0b9, 2020.2.0a11
Notes:
1. Testing was done using VS 2017 15.0.0 and VS 2019 16.5.4
2. VS 2017 was tested with 2019.3.7f1 and has completed the build successfully, whereas VS 2019 would fail every time
-
guavaman
May 07, 2020 19:04
Just to add some information, this is caused by the Visual Studio 2019 16.5 update. Specifically, it is related to the new optimizer used in VS 2019. You can disable this new compiler and continue using VS 2019 by following the directions in this post:
https://forum.unity.com/threads/neverending-il2cpp-build.855235/#post-5703478
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
This is a bug in the Visual Studio 2019 C++ compiler. We have submitted a bug report to Microsoft for this issue:
https://developercommunity.visualstudio.com/content/problem/1021879/clexe-in-vs-2019-returns-1073741819-but-does-not-o.html