Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b8
2018.2.0a1
Issue ID
1005138
Regression
Yes
[Regression] "Unsafe code requires the `unsafe' command line option to be specified" appears in console
How to reproduce:
1. Download and open attached project file
2. Notice the errors in the Console Window
Actual result: In 2018.1.0b7 script works fine, from 2018.1.0b8 error "Assets/LeapMotion/Core/Scripts/Utils/BitConverterNonAlloc.cs(17,7): error CS0227: Unsafe code requires the `unsafe' command line option to be specified" Appears
Reproduced with: 2018.1.0b8, 2018.1.0b9, 2018.2.0a1
Not reproduced with: 2017.3.1p2, 2018.1.0b7
Regression since: 2018.1.0b8, 2018.2.0a1
--------------------------------------------
Solution: This is a change in behaviour. Allow unsafe code option now has to be enabled in player settings for Assembly-CSharp.dll and in the .asmdef inspector for .asmdef assemblies.
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