TLDR: Check multiple references to the same nuget package are all on the same version if you use the Mono linker.
Since my ability to post regularly on things I’m interested in is not great, I figured I could at least post stuff that might be useful.
I recently upgraded a Xamarin iOS app from the “classic” (32bit only) API to the Unified API. After doing so I got the error message:
System.ExecutionEngineException: Attempting to JIT compile method
This is caused by the Xamarin (Mono) linker removing code that is only referenced dynamically. The usual solution is to let the compiler know somehow that you are using the code (using a Preserve attribute if it’s your own code or something like MvvmCross’s LinkerPleaseInclude.cs otherwisr).
In my case, this did not fix the problem. It turns out the Unified API upgrade was a red herring. I had also updated a few nuget packages at the same time. One of them was used in several projects, but I’d missed updating one of them (so I had Project A using v1 of a package and Project B using v2 of a package). This meant my efforts to stop the linker from removing some stuff only worked on one version of the package.