You can now enjoy all the features of Tic-tac-toe Collection, including cross-platform multiplayer on your iPhone and iPad.
Tag: iOS
ListView improvements in Xamarin Forms
Since becoming open source, it has become possible to find out potential upcoming features in Xamarin Forms by just poking around the active branches in the repository (macOS support was visible in the repo before any announcement).
One of them is lv2spike.
From just reading the commit messages, it seems this is a new CollectionView, based on UICollectionView for iOS and RecyclerView for Android.
This is something that has been needed for a while, but is a big enough undertaking that I understand why it has taken a while. After all the branch suggests this is still just a spike.
There are quite a lot of feature requests for the Xamarin Forms ListView that are just not possible (like this one for horizontal layout) mainly because the iOS implementation is based on UITableView. This will open lots of possibilities. My biggest concern is that despite the push forward with features, Xamarin Forms is accruing bugs even faster, and with the expanded platform support this could just get worse…
[SOLVED] System.ExecutionEngineException: Attempting to JIT compile method
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.
