Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.2.3f1
2018.3.0a1
2019.1.0a1
Issue ID
1082185
Regression
Yes
[IL2CPP] Building Development Build fails when Script Debugging is enabled and Scripting Backend is IL2CPP
How to reproduce:
1. Open a new Unity project
2. In the Player Settings, set the Scripting Backend to IL2CPP
3. In the Build Settings, enable Development Build and Script Debugging
4. Click Build button
Expected result: Building is successful.
Actual result: Building fails.
Reproducible with - 2018.2.3f1, 2018.2.9f1, 2018.3.0a1, 2018.3.0a12, 2018.3.0b2, 2019.1.0a1
Not reproducible with - 2018.1.9f2, 2018.2.0f2, 2018.2.2f1
Notes:
- Not tested on versions prior 2018.1, since support for IL2CPP scripting backend for Windows Standalone was not yet introduced.
- On some versions (e.g. 2018.2.9f1) the issue is only reproducible when API Compatibility Levels are set to .NET Standard 2.0.
Fixed in 2019.1.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment