Bug 46170 - Cannot deploy after upgrade to Xcode 8.1
Summary: Cannot deploy after upgrade to Xcode 8.1
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 10.0 (iOS10)
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2016-10-29 23:55 UTC by Shay
Modified: 2016-12-12 07:39 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Shay 2016-10-29 23:55:51 UTC
Compilation works. When trying to deploy, I get  this error:
error HE0003 Could not load the framework libswiftos.dylib
Comment 1 Vincent Dondain [MSFT] 2016-10-30 17:39:42 UTC
Hi Shay, have you updated to latest stable? We pushed updates the Xamarin.iOS and Xamarin Studio this week to add Xcode 8.1 support.

Note: when filing bugs please always include your full build logs, crash reports (if any), test case (to reproduce) and all version informations.

I'm leaving the bug as open as NEEDINFO so you can confirm that new versions of the products fixed your issue or provide us with some more info.
Comment 2 Alex Soto [MSFT] 2016-12-12 07:39:02 UTC
We have not received the requested information. If you are still 
experiencing this issue please provide all the requested information 
and re-open the bug report. Thanks!