Search Issue Tracker
Fixed in 2018.4
Votes
2
Found in
2018.4
2018.4.23f1
Issue ID
1251023
Regression
No
Fatal error in Unity CIL Linker when building to Standalone with Microsoft Maps DLL [2018.4 only]
How to reproduce:
1. Open the attached (BlankProject.zip) project
2. Open the SampleScene
3. Build to Standalone
Expected result: The build succeeds
Actual result: The build fails with a fatal error in Unity CIL Linker
Reproducible with: 2018.4.23f1
Not reproducible with: 2019.3.16f1, 2019.4.0f1, 2020.1.0b12, 2020.2.0a14
Notes:
- The issue is not reproducible on Mono back-end
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
- [Linux] Unity licensing command on Linux doesn't complete when using -batchmode and -nographics
- SerializedReference GameObject property gets set to null after entering Play mode
- Profiler - RawFrameDataIterator ThreadID will always return 0 for profiler frame data loaded from .data files
- Crash on scripting_field_get_type when a Script has List<> of LayoutKind.Explicit struct with [FieldOffset(1)] ScriptableObject
- Frame Debugger doesn't work when using Camera.SetTargetBuffers
Resolution Note (fix version 2018.4):
Fix a crash in UnityLinker that could happen when an invalid security attribute type is encountered
Resolution Note (fix version 2018.4):
Fixed in: 2018.4.27f1