tag:blogger.com,1999:blog-7012931627544824353.post2089776541605884898..comments2023-12-21T05:26:29.269-05:00Comments on Tech Blog: Compiling assemblies for Unity3D using Xamarin 6.x on OSXAntoine AGTHEhttp://www.blogger.com/profile/17440096142681095492noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7012931627544824353.post-25140749689040447512016-08-06T13:35:12.925-04:002016-08-06T13:35:12.925-04:00I found the issue. Unity will crash on start when ...I found the issue. Unity will crash on start when it detects new assemblies to load. Importing assemblies to an Unity project works fine when it is running. Otherwise it crashes for me.Anonymoushttps://www.blogger.com/profile/15811321331203775085noreply@blogger.comtag:blogger.com,1999:blog-7012931627544824353.post-3976237182793065172016-08-06T13:20:24.682-04:002016-08-06T13:20:24.682-04:00Thanks for the info. I have stumbled on the same i...Thanks for the info. I have stumbled on the same issue. The first time I built my library it worked with the MSBuild engine. I simply replaced the missing references with the ones from the Unity.app/Contents folder. Trying my luck I removed the reference to System.Core which didn't seem to be needed. I recompiled and then Unity crashed on start. From then on, I wasn't able to recover my project even with the old mono version. I am working on fixing my problem. Your solution seems to work with a clean project, but in my case it crashed the second time I opened my project imported from 5.3.5 after rebuilding my assemblies.Anonymoushttps://www.blogger.com/profile/15811321331203775085noreply@blogger.com