This thread has now been closed to direct all further updates about this release onto the new Stable release thread:
Visual Studio Extension
Reason for release: Updated SDK bindings and compatibility support for upstream iOS 9.0 and Xcode 7.0 GM versions.
Date published: See https://releases.xamarin.com/.
NOTE: This is a feature release that contains a large number of changes compared to the current Stable version. In addition to support for iOS 9 and Xcode 7, it contains larger changes to the existing parts of Xamarin.iOS than any of the recent smaller service releases. On top of that, as with any Xamarin version that is published in response to an upstream release, these builds have primarily been tested against preview versions of the upstream components. As usual, these "Beta" versions have not yet completed the full suite of tests by the Xamarin QA team. Customer reports of any regressions (or bugs that are incorrectly marked fixed) are still much appreciated, even if the problem would have eventually been caught during the full QA testing process.
You can downgrade back to the current Stable version by switching updater channels.
If needed, you can downgrade back to older versions (from before April 29) by manually reinstalling each old package. See the "Previous versions, downgrading" section on the April 29 Stable release thread for the older downgrade links.
This first post will be updated regularly.
The goal of this thread is to help answer "what might break if I update to this release?"
If you find a new problem that is specific to this version:
a. If you can share some specific error messages or can reproduce the problem consistently, please email the information you have so far to
b. If you only have a general description of the problem, you can post it directly on this forum thread so that hopefully a member of the Xamarin team or another user will recognize it and be able to help fill in some details.
Non-public Bug 33984 - [XamarinVS] [iOS] Building an iOS class library that uses string resources fails with an error similar to "Error reading resource ... MyStrings.strings ... The system cannot find the path specified."
Non-public Bug 33819 - [XamarinVS] [iOS] Attempting to stop a WatchKit app in Glance mode does not stop the app.
Non-public Bug 31424 - [Xamarin Studio] [iOS] Classic API on Mac only: "Resource rules files "" not found". Partial workaround: Enable "Project Options -> General -> Use MSBuild build engine (unsupported for this project type)" and clean and rebuild the project. (The MSBuild build engine does now work for many Classic API projects.)
Non-public Bug 33880 - [Upstream] [iOS] Attempting to stop a WatchKit app in Notification mode does not stop the app. (The same problem occurs with an Objective-C or Swift app deployed from Xcode, so this is an upstream issue.)
Non-public Bug 33888 - [XamarinVS] [iOS] VS 2010 only. Opening a second Xamarin.iOS solution when already connected to the build host causes VS to disconnect from the build host. The user must refresh the connection manually via the "Refresh build server info" button.
-linkskip=System.Threading.Tasksunder "project options -> iOS Build -> Additional mtouch arguments".
-all_loadlinker flag (via either
LinkerFlags) try removing it.
.dllfiles: "Could not copy "... PortableClassLibrary1.dll" to "bin\Debug\PortableClassLibrary1.dll". Exceeded retry count of 10. Failed." This is a different problem than Bug 26841 because it affects
.dllfiles rather than
.dll.mdbfiles. It appears to be less common than Bug 26841. The results to date suggest that it is a bug in Visual Studio itself rather than in the Xamarin extensions. For example, it appears to be possible to hit the problem using a Windows Phone project, with no Xamarin involvement at all. The recent changes to the Xamarin "Clean project" process to properly remove stale files might have caused this to become easier to hit with Xamarin projects. In any case, it is still under investigation.
(For issues that might behave differently for some customers after updating to this new release, or that might be difficult to find via Bugzilla.)
Bug 28027 - [XamarinVS] [iOS] The debugger sometimes fails to connect properly after the app launches. This means breakpoints will not be hit during that launch of the app and the "Output -> Debug" window will be blank. Repeating the steps of (a) stopping the debugger and (b) relaunching the app will eventually lead to a successful connection. This problem has existed since at least XamarinVS 3.9.483, but some recent reports suggest that it has become more common for certain users recently. The problem might be caused by a race condition. Based on that guess, the recent releases might have changed some timings and increased the probability of hitting the issue on a wider range of system configurations. The bug is under active investigation.
EDIT Sep 11: XamarinVS installer now available. Add forum discussion 50492.
EDIT Sep 14: Remove iOS Bug 33853 (fixed). Relabel iOS Bug 33880 as upstream. Add XamarinVS.iOS Bug 33884.
EDIT Sep 16: Update for new builds. Add Mac-only iOS Bug 31424. Remove XamarinVS.iOS Bug 33884 (fixed). Add XamarinVS.iOS bugs 33984 and 33819.