Hello,
We have a Xamarin.Forms app targeting iOS, Android, and UWP. We're using a PCL for our common Xamarin.Forms code. We're on an older version of the Xamarin.Forms library (version 2.3.4.231).
I recently tried updating the Nuget packages for all projects in our solution to the latest Xamarin.Forms library (version 2.5.0.122203). Everything works fine in iOS and Android. However, when I attempt to run a UWP Debug x86 build on the local machine, the app crashes immediately. I have attached what I see from the event log.
Here is the project.json file (before updating packages):
{
"dependencies": {
"Acr.UserDialogs": "6.3.10",
"Microsoft.NETCore.UniversalWindowsPlatform": "5.2.2",
"modernhttpclient": "2.4.2",
"PCLCrypto": "2.0.147",
"Plugin.Permissions": "1.2.1",
"Splat": "1.6.2",
"Xam.Plugin.Connectivity": "2.2.12",
"Xam.Plugin.Geolocator": "3.0.4",
"Xam.Plugin.Media": "2.6.1",
"Xamarin.Forms": "2.3.4.231",
"Xamarin.Insights": "1.12.3"
},
"frameworks": {
"uap10.0": {}
},
"runtimes": {
"win10-arm": {},
"win10-arm-aot": {},
"win10-x86": {},
"win10-x86-aot": {},
"win10-x64": {},
"win10-x64-aot": {}
}
}
And after:
{
"dependencies": {
"Acr.UserDialogs": "6.3.10",
"Microsoft.NETCore.UniversalWindowsPlatform": "6.0.6",
"modernhttpclient": "2.4.2",
"PCLCrypto": "2.0.147",
"Plugin.Permissions": "2.2.1",
"Splat": "1.6.2",
"Xam.Plugin.Connectivity": "3.0.3",
"Xam.Plugin.Geolocator": "4.2.0",
"Xam.Plugin.Media": "3.1.2",
"Xamarin.Forms": "2.5.0.122203",
"Xamarin.Insights": "1.12.3"
},
"frameworks": {
"uap10.0.14393": {}
},
"runtimes": {
"win10-arm": {},
"win10-arm-aot": {},
"win10-x86": {},
"win10-x86-aot": {},
"win10-x64": {},
"win10-x64-aot": {}
}
}
If I change the Xamarin.Forms dependency back to a version 2.3.XXX variant the app will not immediately crash on startup. However, because a later version of Xamarin.Forms is being used by our PCL, the app doesn't work quite right at runtime (e.g. Device.Runtime is Windows instead of UWP). I also tried 2.4.XXX variants of the Xamarin.Forms dependeny in our UWP app - those fail too.
Is this a known issue? Anybody know how to resolve this?
Thanks.