Using with Xamarin.Forms about xamarin.swift

[Flash3001]

Hey @Niach, I never worked with Xamarin.Forms before, but based on the message it seems the code for MSBuild responsible for copying the Simulator frameworks from the SimulatorFrameworks folder to the Frameworks folder is not running.

If you deploy to a device it works? If I'm correct it should as this project puts the Device files in the Frameworks folder by default.

When you add the Xamarin.Swift4 base package it changes you .csproj to run this file manipulation code.

You can find a line like this one in your .csproj
<Import Project="..\packages\Xamarin.Swift4.4.0.0.0\build\Xamarin.Swift4.targets" Condition="Exists('..\packages\Xamarin.Swift4.4.0.0.0\build\Xamarin.Swift4.targets')" />

Please check the Xamarin.Forms project to see if it includes this line and if it runs on the Device.

[gmoney494]

I also have a similar issue with the same crash report on my custom binding for a library partially written in swift. My .csproject did not have the line you mentioned @Flash3001. I added it and i still get the same error (I did have to change the file location to the global nuget packages folder since i dont have a local project one). Not sure what else i can do to get past this.

PS. Ive added the necessary swift libraries using the otool to figure out the depedencies. Also using swift 4 packages. This is also a xamarin forms app. Without the libswiftcore , i get the library missing error, with them, now it says wrong architecture. this is for running on the simulator, the framework contains the x86_64 simulator architecture.

[Flash3001]

Hey @gmoney494.

The crash is complain the Swift libraries contains the wrong architecture or your binding library itself?

What happens if you try to run on a real device?

[valentingrigorean]

Hey editing csproj and adding <Import Project="..\packages\Xamarin.Swift4.4.0.0.0\build\Xamarin.Swift4.targets" Condition="Exists('..\packages\Xamarin.Swift4.4.0.0.0\build\Xamarin.Swift4.targets')" /> did fix my problem. Be careful with the path to packages to be correct.

Thanks @Flash3001