Search Issue Tracker
Fixed in 2018.4.X
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
Comments (2)
-
Gidcheen
Jan 11, 2022 18:30
not fixed
-
prabakarsjn
May 14, 2021 13:30
not fixed same error open in unity 2021.4
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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