Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.33f1
6000.0.6f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-74101
Regression
Yes
Newtonsoft Mono.Linker.LinkerFatalErrorException exception is thrown when building Android player
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the Build Settings window (File > Build Settings)
3. Make sure “Android” is the selected platform
4. Build the project
5. Observe the Console window
Expected result: The build finishes successfully
Actual result: An exception is thrown {{Mono.Linker.LinkerFatalErrorException: C:\...\Assets\TestNewtonsoft.cs(11,9): error IL1005: .TestNewtonsoft.Start(): Error processing method '.TestNewtonsoft.Start()' in assembly 'Assembly-CSharp.dll'}}
Reproducible with: 2022.2.0b10, 2022.2.21f1, 2022.3.33f1, 6000.0.6f1
Not reproducible with: 2021.3.39f1, 2022.2.0b9
Reproducible on: Windows 10
Not reproducible on: No other environment tested
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:
dynepic.MOTAR.json.dll is actually another instance of Newtonsoft.json.dll. Assembly filename and assembly name need to match to properly resolve the assemblies while we run our tools.
Resolution Note:
dynepic.MOTAR.json.dll is actually another instance of Newtonsoft.json.dll. Assembly filename and assembly name need to match to properly resolve the assemblies while we run our tools.